Dynamic transaction card protected by gesture and voice recognition

ABSTRACT

A dynamic transaction card that includes a transaction card having a number of layers, each of which may be interconnected to one another. For example, a dynamic transaction card may include an outer layer, a potting layer, a sensor layer that may be utilized to activate a dynamic transaction card by authenticating the card user as authorized to use the card through user authentication input recognition, which may be gesture and voice recognition processing, a display layer (including, for example, LEDs, a dot matrix display, and the like), a microcontroller storing firmware, Java applets, Java applet integration, and the like, an EMV™ chip, an energy storage component, one or more antenna (e.g., Bluetooth™ antenna, NFC antenna, and the like), a power management component, a flexible printed circuit board (PCB), a chassis, and/or a card backing layer.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation-in-part of U.S. patentapplication Ser. No. 15/098,585, filed Apr. 14, 2016, which claims thebenefit of U.S. Provisional Application No. 62/147,568 entitled “ASystem, Method, and Apparatus for a Dynamic Transaction Card” filed Apr.14, 2015; and U.S. Provisional Application No. 62/270,669 entitled “ASystem, Method, and Apparatus for a Dynamic Transaction Card” filed Dec.22, 2015. The entire contents of these applications are incorporatedherein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates to a dynamic transaction card and thesystems and methods relating to the dynamic transaction card. A dynamictransaction card may include components such as LEDs or light pipesembedded in the transaction card, an input mechanism, networkingtechnologies, memory for storing transaction rules, transaction cardpreferences, applications, and/or a hearing and/or visual impairmentinput/output interface for a dynamic transaction card, and sensors thatmay be used to activate a dynamic transaction card by authenticating thecard user as authorized to use the card through user authenticationinput recognition, which may be gesture and voice recognitionprocessing.

BACKGROUND OF THE DISCLOSURE

The entire contents of the following applications are incorporatedherein by reference: U.S. Provisional Application No. 62/266,324entitled “Printed Circuit Board with Integrated Battery” filed Dec. 11,2015; U.S. Provisional Application No. 62/270,307 entitled “CapacitivePowertrain for a Smart Card” filed Dec. 21, 2015; U.S. ProvisionalApplication No. 62/305,599 entitled “Smart Card EuroPay Master Card Visa(“EMV”) Terminal Energy Harvesting” filed Mar. 9, 2016; U.S. patentapplication Ser. No. 14/977,730 entitled “A System, Method, andApparatus for Locating a Bluetooth Enabled Transaction Card, filed Dec.22, 2015, which claims the benefit of U.S. Provisional Application No.62/095,190, filed on Dec. 22, 2014; U.S. Pat. No. 9,105,025, entitled,Enhanced Near Field Communications Attachment filed on May 29, 2014,which claims the benefit of U.S. Provisional Application No. 61/570,275filed on Dec. 13, 2011 and U.S. Provisional Application No. 61/547,910filed on Oct. 17, 2011; U.S. Provisional Application No. 62/147,568,filed on Apr. 14, 2015, application Ser. No. 14/338,423, entitled“System and Method for Exchanging Data with Smart Cards” filed Jul. 23,2014, which claims the benefit of U.S. Provisional Application No.61/857,443 filed on Jul. 23, 2013; and U.S. Provisional Application No.62/270,648 entitled “Smart Card with EMV Interface and Method ofManufacturing” filed Dec. 22, 2015.

Transaction cards, such as credit cards or debit cards, have limitedcapabilities. Transaction cards may include a magnetic stripe capable ofstoring data by modifying the magnetism of magnetic particles on thestripe. The magnetic stripe may include several tracks of data(typically track 1, track 2, and track 3) storing data about thetransaction card owner or data about the account number or expirationdate of an associated account.

Transaction cards may also include a secure payment chip, which may be aEuroPay-MasterCard-Visa standard compliant (“EMV™”) chip, or “EMV™chip”. The EMV™ chip in an EMV™ card may communicate with EMV™-compliantterminals to conduct secure transactions. For example, information maybe exchanged between the card and the terminal via the EMV™ chip, whichmay also require the entry of a PIN to complete a transaction. Thesecure payment chip, which may be an EMV™ chip, may dynamically storedata previously stored on a magnetic strip, allowing for increasedsecurity associated with transaction cards.

However, EMV™ and magnetic stripe cards have limited capabilities, suchas limited display capabilities, limited transaction capabilities, andlimited processing capabilities, and limited security capabilities. Forexample, there is a high occurrence of fraud for card presenttransactions. An additional layer of security to authenticate a carduser as authorized to use the care is needed. For example, currentpayment card authorization may only require signature verification.However, signatures are easily forged and also not frequently checked.Authorization may also include requiring a cardholder to input a PINcode, but this is limited to 4-6 characters, which may be repetitive andeasy to guess.

These and other drawbacks exist.

SUMMARY OF THE DISCLOSURE

Various embodiments of the present disclosure provide a dynamictransaction card, systems supporting a dynamic transaction card, andmethods for operating a dynamic transaction card.

As referred to herein, a dynamic transaction card may be understood toinclude a transaction card that may include a number of accounts thatmay be activated and/or deactivated by an account holder and/or accountprovider, data storage that may be updated to reflect real-time and/oron-demand account and/or transaction data, and/or display components todisplay the updated account and/or transaction data. A dynamictransaction card may be understood to be activated (e.g., turned on)and/or deactivated (e.g., turned off) based on input received at thedynamic transaction card as described herein.

In an example embodiment, a dynamic transaction card may include atransaction card having a number of layers, each of which may beinterconnected. For example, a dynamic transaction card may include anouter layer, a potting layer, a sensor layer (e.g., touch sensor layer),a display layer (including, for example, LEDs, a dot matrix display, andthe like), a microcontroller storing firmware, Java applets, Java appletintegration, and the like, a secure payment chip, which may be an EMV™chip, an energy storage component (e.g., battery), one or more antenna(e.g., Bluetooth® antenna, NFC antenna, and the like), a powermanagement component, a flexible printed circuit board (PCB), a chassis,and/or a card backing layer. An EMV™ chip may include an EMV™ processorand an EMV™ plate. An EMV™ processor may be within a dynamic transactioncard and placed at any location within the transaction card. An EMV™processor may be connected to an EMV™ plate, which may be placed on theexternal surface of the dynamic transaction card. An EMV™ plate may beconfigured to connect with the contact points of an EMV™ reader.

A dynamic transaction card may include a secure payment processor, whichmay be an EMV™ processor, in communication with an applet and/orapplication on the dynamic transaction card. For example, data may becommunicated between the secure payment processor and the applet and/orapplication in a secure manner so that an applet and/or applicationresiding within the dynamic transaction card may receive transactiondata, account data, and/or account holder data, process the receiveddata (e.g., compare received data to stored data, calculate a newaccount balance, calculate a new budget balance, calculate a new limit,store a new account balance, store a new budget balance, store a newlimit, store transaction data, and/or the like). A number ofconfigurations may be used to transmit and/or receive data between anapplet/application and a secure payment processor on a dynamictransaction card.

In an example embodiment, a system supporting a dynamic transaction cardmay include a dynamic transaction card, a mobile device, a securepayment terminal which may be an EMV™ terminal, and/or a financialinstitution system connected over network connections (e.g., Internet,Near Field Communication (NFC), Radio Frequency Identification (RFID),Bluetooth™, including Bluetooth™ Low Energy (BLE) and/or the like). Amobile device may include, for example, a smartphone, tablet, phablet,laptop, or the like. A mobile device may include Near FieldCommunication (NFC) hardware and software components, Bluetooth™input/output hardware and software, and one or more processors, variousinput/output interfaces, and/or systems, such as transaction processingsystems and account systems. These layers and/or components may becombined where appropriate. For example, a potting layer may be combinedwith display components to create a more elaborate display component forthe EMV′ card.

An EMV™ terminal may include an input slot to receive an EMV™ card, anEMV′ reader, a display, a processor, an input/output component, one ormore antenna (e.g., antenna supporting NFC, RFID, Bluetooth™, WiFiDirect, and/or the like), memory, a magnetic stripe reader, and/or thelike.

In an example embodiment, a financial institution system may include anumber of servers and computers, each equipped with storage andcomponents programmed with various capabilities, such as, storingcardholder data, transaction processing, and/or the like. Thesecomponents may be understood to refer to computer executable software,firmware, hardware, and/or various combinations thereof.

A dynamic transaction card may include a number of interactivecomponents, including for example, components that may execute on amicroprocessor, which may interact with an a secure payment chip, whichmay be an EMV™ chip via an Application Program Interface (API) definedfor the secure payment chip. By interacting with the secure paymentchip, the microprocessor could run applications, such as an applicationthat allows a customer to select a particular financial account to usewhen executing a transaction, applications that alert a customer of anaccount balance, applications that allow a customer to view accountinformation (e.g., recent transactions, spending per category, budgetinginformation, and/or the like), applications that allow customers toactivate an additional account (e.g., where a customer has an existingdebit account, that customer may activate a new credit account), and/orother applications that allow a customer to interact with an accountand/or account data. By way of example, an application may allow acustomer to select from a credit account, a savings account, a debitaccount, and/or the like, where each account has information regardingthe account stored on the microprocessor. As described herein, anapplication may generate a display (e.g., dot matrix, LED display, OLEDdisplay, and/or the like) to illustrate various features of an accountsuch as account data (e.g., account balance, account limit, transactionhistory, budget balance, budget limit, and/or the like) and/ortransaction data (e.g., transaction amount, effect of transaction on abudget and/or account balance, and/or the like).

Additionally, data for display may be received at the dynamictransaction card via the antenna from, for example, a mobile device inconnection with the dynamic transaction card. For example, uponreceiving a request to power-up or activate the dynamic transaction cardvia, for example, a sensor or other input mechanism, the dynamictransaction card may request connection to a mobile device via anantenna (e.g. a Bluetooth™ antenna, an NFC antenna, and/or the like).Upon establishing a secure connection between the dynamic transactioncard and a mobile device, the dynamic transaction card may requestupdated account information for accounts stored on the dynamictransaction card. A mobile device may store an application associatedwith the financial institution that maintains the account(s) associatedwith the dynamic transaction card and, upon receiving a request forupdated account information from the dynamic transaction card, thefinancial institution application stored on the mobile device may beactivated to request updated financial account information from abackend system of the financial institution maintaining the account. Thefinancial institution application on the mobile device allows for asecure connection to be established between the mobile device and abackend system of the financial institution.

A financial institution application running on a user device may requirea user to enter one or more credentials before requesting informationfrom a backend system. For example, credentials may include userauthentication credentials, which may be a user authentication input,such as for example, a password entry, PIN, gesture, which may include amotion, tap, rotation, button press, a signature entry, symbol, and/orbiometric data (fingerprint, facial recognition, and the like). Afinancial institution application running on a mobile device may receivedata from a dynamic transaction card that allows the application tocommunicate with a financial institution backend to receive updatedinformation without received credentials input on the mobile device. Forexample, a mobile device and dynamic transaction card may be paired toeach other such that once the dynamic transaction card and mobile deviceare paired, a secure communications channel may be established for allfuture communications. An account holder may control these featuresusing device settings (e.g., iOS or Android settings that managesecurity and/or application settings) and/or mobile application(s)associated with the financial institution maintaining the account. Thefinancial institution also may rely on the fact that a dynamictransaction is paired with a mobile device to enable requestinginformation from a backend system by the mobile device. In this example,the dynamic transaction card may include security features that enablethe dynamic transaction card to pair with a mobile device. U.S. patentapplication Ser. No. 14/290,347, filed on May 29, 2014, the entirecontents of which are incorporated herein by reference, describesexample methods for pairing a contactless attachment with a mobiledevice. U.S. application Ser. No. 14/977,730, filed on Dec. 22, 2015,the entire contents of which are incorporated herein by reference,describes example methods and systems for pairing a transaction cardwith a mobile device.

For example, a dynamic transaction card may receive input from a sensorsuch as a capacitive touch sensor, a piezoelectric sensor, via loadcells, an accelerometer, gyroscope, light sensor, fingerprint sensors,MEMS (Micro Electro Mechanical Systems) microphone and/or the like. Themicrophone may be constructed out of a bimorph element such as a bimorphcrystal. The microphone may also be constructed out of a piezoelectricelement. The input component (e.g., sensor) may be located at anyposition on the dynamic transaction card. For example, an inputcomponent may be located around the edges of a dynamic transaction cardand/or at a particular point on a dynamic transaction card. Amicrophone, for example may include a hole for sound to pass into themicrophone, and as such a microphone may be positioned such that adynamic transaction card has a pass through for this hole. An input mayinclude a security feature, such as a biometric feature (e.g.,fingerprint, eye scan, voice recognition, and/or the like). For example,a sensor may include technology to receive a security input, similar tothe Apple® Touch ID which reads a fingerprint to activate features of amobile device such as payment and unlocking a device. A sensor may alsoinclude technology to receive a user authentication input, which may bea gesture and a voiceprint of a user of the card, which may activate thedynamic transaction card utilizing user authentication inputrecognition, which may be gesture and voice recognition by amicrocontroller to authenticate a card user as authorized to use thecard.

Upon receiving the input, a dynamic transaction card may generate andtransmit a request for information associated with the accounts storedon the dynamic transaction card. In generating and/or transmitting arequest for information associated with the accounts stored on thedynamic transaction card, the information may be displayed as describedherein. Accordingly, the information may be displayed upon receiving anytype of input as described herein.

The accounts stored on the dynamic transaction card may be related toany transaction account associated with a financial institution. In anexample embodiment, the dynamic transaction card also may store accountsrelated to multiple financial institutions. The dynamic transaction cardmay store account identifiers (e.g., account number, account ID, accountnickname, account holder name, account holder ID, and/or the like),account balance data (e.g., account balance, spending limit, dailyspending limit, and/or the like), recent transaction data (e.g.,transaction amount, merchant name, transaction date, transaction time,and/or the like), and/or account history data (e.g., payment amounts,payment dates, transaction history, and/or the like). The dynamictransaction card also may receive data via a mobile device and/orfinancial institution backend upon request to reduce the amount of datastored on the dynamic transaction card.

In order to receive and transmit data, a dynamic transaction card mayinclude, for example, NFC, WiFi Direct and/or Bluetooth™ technologies,such as various hardware and software components that use Bluetooth™, ora wireless technology standard for exchanging data over short distances.Bluetooth™, WiFi Direct or NFC technology may include technology totransmit data using packets, such that each packed is transmitted over achannel. For example, a Bluetooth™ channel may have a bandwidth of 1 MHzor 2 MHz with the number of channels being 79 or 40, respectively.Hardware that may be included in Bluetooth™, WiFi Direct, and/or NFCtechnology includes a Bluetooth™/NFC/WiFi Direct device or chipset witha transceiver, a chip, and an antenna. The transceiver may transmit andreceive information via the antenna and an interface. The chip mayinclude a microprocessor that stores and processes information specificto a dynamic transaction device and provides device controlfunctionality. Device control functionality may include connectioncreation, frequency-hopping sequence selection and timing, powercontrol, security control, polling, packet processing, and the like.

Once data is received at a dynamic transaction card, the data may bedisplayed and/or an indication of the data may be displayed via thedisplay components in the dynamic transaction card. For example, aseries of LED lights and/or light pipes may indicate a balanceassociated with an account via color, via the number of LED lightsilluminated, via a pattern of illumination, and/or the like. As anotherexample, a dot matrix may display various alphanumeric characters todisplay account data, transaction data, and/or any other data requestedfrom an account holder in possession of the dynamic transaction card.

A dynamic transaction card may remain active until a user deactivates aninput associated with the dynamic transaction card (e.g., removing inputfrom the capacitive touch sensors, piezoelectric sensors and/or loadcells). A dynamic transaction card may remain active until a userprovides additional input to input components associated with thedynamic transaction card (e.g., by touching for a second time acapacitive touch sensor, and/or the like).

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure, together with furtherobjects and advantages, may best be understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings, in the several Figures of which like reference numeralsidentify like elements, and in which:

FIG. 1 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 2 depicts an example embodiment of a dynamic transaction cardaccording to embodiments of the disclosure;

FIG. 3 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 4 depicts an example card-device linking system according toembodiments of the disclosure; and

FIG. 5 depicts an example method for using a dynamic transaction cardaccording to embodiments of the disclosure.

FIG. 6 depicts an example method for using a dynamic transaction cardaccording to embodiments of the disclosure;

FIG. 7 depicts an example embodiment of a dynamic transaction cardaccording to embodiments of the disclosure;

FIG. 8 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 9 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 10 depicts an example embodiment of a method including a dynamictransaction card according to embodiments of the disclosure;

FIG. 11 depicts an example embodiment of a method including a dynamictransaction card according to embodiments of the disclosure;

FIG. 12 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 13 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 14 depicts an example embodiment of a system including a dynamictransaction card according to embodiments of the disclosure;

FIG. 15 depicts an example embodiment of a method for conducting atransaction associated with a dynamic transaction card according toembodiments of the disclosure;

FIG. 16 depicts an example embodiment of a method for detecting fraudassociated with a dynamic transaction card according to embodiments ofthe disclosure;

FIG. 17 depicts an example embodiment of a method for providing displaysettings of a dynamic transaction card according to embodiments of thedisclosure;

FIG. 18 depicts an example embodiment of a method for providing displaysettings of a dynamic transaction card according to embodiments of thedisclosure;

FIG. 19 depicts an example method for using gesture recognition toactivate a dynamic transaction card according to embodiments of thedisclosure; and

FIG. 20 depicts an example method for using voice recognition toactivate a dynamic transaction card according to embodiments of thedisclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following description is intended to convey a thorough understandingof the embodiments described by providing a number of specific exampleembodiments and details involving a dynamic transaction card and systemsand methods for using a dynamic transaction card. It should beappreciated, however, that the present disclosure is not limited tothese specific embodiments and details, which are examples only. It isfurther understood that one possessing ordinary skill in the art, inlight of known systems and methods, would appreciate the use of theinvention for its intended purposes and benefits in any number ofalternative embodiments, depending on specific design and other needs. Afinancial institution and system supporting a financial institution areused as examples for the disclosure. The disclosure is not intended tobe limited to financial institutions only. For example, many otheraccount providers may exist, such as retail stores, loyalty programs,membership programs, transportation providers (e.g., a fare card), ahousing provider, and the like.

Additionally, an EMV™ card is used as an example of a dynamictransaction card. A dynamic transaction card may include any type oftransaction card that includes a microcontroller-enabled card used inany type of transaction, including, for example, debit cards, creditcards, pre-paid cards, cards used in transportation systems, membershipprograms, loyalty programs, hotel systems, and the like. A dynamictransaction card may include enhanced features, including hardware,software, and firmware, beyond the traditional features of a magneticstripe or EMV™ card. The use of “mobile device” in the examplesthroughout this application is only by way of example. Any type ofdevice capable of communicating with a dynamic transaction card may alsobe used, including, for example, personal computers, tablets, gamingsystems, televisions, or any other device capable of communicating witha dynamic transaction card.

According to the various embodiments of the present disclosure, adynamic transaction card and systems and methods for using a dynamictransaction card are provided. Such embodiments may include, forexample, a transaction card including various components to facilitatethe notifications, alerts, and/or other output on a dynamic transactioncard to an account holder associated with the dynamic transaction card.Notifications, alerts, and output may be provided in the form of LEDlights and/or colors, LED lighting patterns, dot matrix displays, and/orthe like, which as situated on and/or within a dynamic transaction card.Interactive elements of a dynamic transaction card may be activated,triggered, and/or made available via an input component on the dynamictransaction card. For example, a dynamic transaction card may include acapacitive touch sensor, a piezoelectric sensor, an accelerometer,gyroscope, light sensor, fingerprint sensors, MEMS (Micro ElectroMechanical Systems) microphone, via load cells, and/or the like. Thesetypes of sensors may activate, trigger, and/or make available displayand/or LED lighting information to alert and/or notify a dynamictransaction card holder.

In various embodiments, providing the alerts, notifications, and/orother output on a dynamic transaction card could be provided with theassistance of a network environment, such as a cellular or Internetnetwork. For example, a mobile device may request and/or receive dataindicative of notifications, alerts, and/or output to be displayed on adynamic transaction card from a financial institution system via anetwork. A mobile device may then relay the data via a network (e.g.,NFC, Bluetooth™, and/or the like) to the dynamic transaction card forstorage and/or to activate, trigger, and/or output notifications and/oralerts.

FIG. 1 depicts an example system 100 including a dynamic transactioncard. As shown in FIG. 1, an example system 100 may include one or moredynamic transaction cards 120, one or more account provider systems 130,one or more user devices 140, and one or more merchant systems 150connected over one or more networks 110.

For example, network 110 may be one or more of a wireless network, awired network or any combination of wireless network and wired network.For example, network 110 may include one or more of a fiber opticsnetwork, a passive optical network, a cable network, an Internetnetwork, a satellite network, a wireless LAN, a Global System for MobileCommunication (“GSM”), a Personal Communication Service (“PCS”), aPersonal Area Network (“PAN”), Wireless Application Protocol (WAP),Multimedia Messaging Service (MMS), Enhanced Messaging Service (EMS),Short Message Service (SMS), Time Division Multiplexing (TDM) basedsystems, Code Division Multiple Access (CDMA) based systems, D-AMPS,Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g,a Bluetooth™ network, or any other wired or wireless network fortransmitting and receiving a data signal.

In addition, network 110 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (“WAN”), alocal area network (“LAN”), a wireless personal area network (“WPAN”),or a global network such as the Internet. Also network 110 may supportan Internet network, a wireless communication network, a cellularnetwork, or the like, or any combination thereof. Network 110 mayfurther include one network, or any number of the example types ofnetworks mentioned above, operating as a stand-alone network or incooperation with each other. Network 110 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively coupled. Network 110 may translate to or from otherprotocols to one or more protocols of network devices. Although network110 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 110 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

User device 140 and/or merchant system 150 may include, for example, oneor more mobile devices, such as, for example, personal digitalassistants (PDA), tablet computers and/or electronic readers (e.g.,iPad, Kindle Fire, Playbook, Touchpad, etc.), wearable devices (e.g.,Google Glass), telephony devices, smartphones, cameras, music playingdevices (e.g., iPod, etc.), televisions, set-top-box devices, and thelike.

Account provider system 130, user device 140, and/or merchant system 150also may include a network-enabled computer system and/or device. Asreferred to herein, a network-enabled computer system and/or device mayinclude, but is not limited to: e.g., any computer device, orcommunications device including, e.g., a server, a network appliance, apersonal computer (PC), a workstation, a mobile device, a phone, ahandheld PC, a personal digital assistant (PDA), a thin client, a fatclient, an Internet browser, or other device. The network-enabledcomputer systems may execute one or more software applications to, forexample, receive data as input from an entity accessing thenetwork-enabled computer system, process received data, transmit dataover a network, and receive data over a network. For example, accountprovider system may include components such as those illustrated in FIG.3 and/or FIG. 9. Merchant system may include, for example, componentsillustrated in FIG. 8 and/or FIG. 9.

Account provider system 130, user authentication system 160, user device140, and/or merchant system 150 may include at least one centralprocessing unit (CPU), which may be configured to execute computerprogram instructions to perform various processes and methods. Accountprovider system 130, user device 140, and/or merchant system 150 mayinclude data storage, including for example, random access memory (RAM)and read only memory (ROM), which may be configured to access and storedata and information and computer program instructions. Data storage mayalso include storage media or other suitable type of memory (e.g., suchas, for example, RAM, ROM, programmable read-only memory (PROM),erasable programmable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), magnetic disks, optical disks,floppy disks, hard disks, removable cartridges, flash drives, any typeof tangible and non-transitory storage medium), where the files thatcomprise an operating system, application programs including, forexample, web browser application, email application and/or otherapplications, and data files may be stored. The data storage of thenetwork-enabled computer systems may include electronic information,files, and documents stored in various ways, including, for example, aflat file, indexed file, hierarchical database, relational database,such as a database created and maintained with software from, forexample, Oracle® Corporation, Microsoft® Excel file, Microsoft® Accessfile, a solid state storage device, which may include an all flasharray, a hybrid array, or a server-side product, enterprise storage,which may include online or cloud storage, or any other storagemechanism.

Account provider system 130, user authentication system 160, user device140, and/or merchant system 150 may further include, for example, aprocessor, which may be several processors, a single processor, or asingle device having multiple processors. Although depicted as singleelements, it should be appreciated that according to one or moreembodiments, account provider system 130, user authentication system160, user device 140, and/or merchant system 150 may comprise aplurality of account provider systems 130, user devices 140, and/ormerchant systems 150.

Account provider system 130, user authentication system 160, user device140, and/or merchant system 150 may further include data storage. Thedata storage may include electronic information, files, and documentsstored in various ways, including, for example, a flat file, indexedfile, hierarchical database, relational database, such as a databasecreated and maintained with software from, for example, Oracle®Corporation, Microsoft® Excel file, Microsoft® Access file, a solidstate storage device, which may include an all flash array, a hybridarray, or a server-side product, enterprise storage, which may includeonline or cloud storage or any other storage mechanism.

As shown in FIG. 1, each account provider system 130, userauthentication system 160 user device 140, and/or merchant system 150may include various components. As used herein, the term “component” maybe understood to refer to computer executable software, firmware,hardware, and/or various combinations thereof. It is noted there where acomponent is a software and/or firmware component, the component isconfigured to affect the hardware elements of an associated system. Itis further noted that the components shown and described herein areintended as examples. The components may be combined, integrated,separated, or duplicated to support various applications. Also, afunction described herein as being performed at a particular componentmay be performed at one or more other components and by one or moreother devices instead of or in addition to the function performed at theparticular component. Further, the components may be implemented acrossmultiple devices or other components local or remote to one another.Additionally, the components may be moved from one device and added toanother device, or may be included in both devices.

As depicted in FIG. 1, system 100 may include a dynamic transaction card120. A dynamic transaction card may include any transaction card that isable to display alerts, notifications, and/or other output to a cardholder via a display and/or LED lighting 126 and/or receive input tointeract with the dynamic transaction card via, for example, a sensor124. Although FIG. 1 depicts a single sensor, 124, multiple sensors maybe included in dynamic transaction card 124. Dynamic transaction card120 also may be composed of various materials that enable the entireexterior surface of card 120 to act as a sensor. A dynamic transactioncard may be able to communicate with, for example, a mobile device usingRFID, Bluetooth™, NFC, WiFi Direct and/or other related technologies.For example, communications between a dynamic transaction card and amobile device may include methods, systems, and devices described inU.S. patent application Ser. No. 14/338,423 filed on Jul. 23, 2014, theentire contents of which are incorporated herein by reference.

A dynamic transaction card may be able to communicate with EMV™terminals via contact points positions on the exterior of card 120, suchas those positions on an EMV™ chip 122 located on the dynamictransaction card 120 or an EMV™ plate positions on the exterior of card120 connected to an EMV™ processor within card 120. For example, contactpoints position on the exterior of card 120 may be directly connectedand adjacent to an EMV′ processor (e.g., EMV™ chip 122). In anotherexample, the contact points positions on the exterior of card 120 may beconnected to an EMV™ processor sing a form of wired connection (e.g.,electrical wiring, plastic jumpers, and/or the like) such that the EMV™processor may be positioned at any location in the interior of card 120as described in U.S. Provisional Application 62/270,648, the entirecontents of which are incorporated herein by reference.

A dynamic transaction card 120 may also include hardware components toprovide contactless payments and/or communications. For example, dynamictransaction card 120 may include an output layer, an outer protectivelayer, potting, application (e.g., a Java Applet), applicationintegration (e.g., Java Applet integration), an EMV™ chip 122, one ormore sensors, a display, a display driver, firmware, a bootloader, amicrocontroller, one or more antenna, an energy storage component, powermanagement, a flexible PCB, a chassis, and/or card backing asillustrated in FIGS. 2 and 7. An EMV™ chip 122 embedded in the dynamictransaction card 120 may include a number of contacts that may beconnected and activated using an interface device.

Account provider system 130 may include systems associated with, forexample, a banking service company such as Capital One®, Bank ofAmerica®, Citibank®, Wells Fargo®, Sun Trust, various community banks,and the like, as well as a number of other financial institutions suchas Visa®, MasterCard®, and American Express® that issue credit and/ordebit cards, for example, as transaction cards. Account provider system130 may include and/or be connected to one or more computer systems andnetworks to process transactions. For example, account provider system130 may process transactions as shown and described in FIGS. 3 and 9below. Account provider system 130 may include systems associated withfinancial institutions that issue transaction cards, such as a dynamictransaction card 120, and maintains a contract with cardholders forrepayment. In various embodiments, an account provider system 130 mayissue credit, debit, and/or stored value cards, for example. Accountprovider system 130 may include, by way of example and not limitation,depository institutions (e.g., banks, credit unions, building societies,trust companies, mortgage loan companies, pre-paid gift cards or creditcards, etc.), contractual institutions (e.g., insurance companies,pension funds, mutual funds, etc.), investment institutions (e.g.,investment banks, underwriters, brokerage funds, etc.), and othernon-bank financial institutions (e.g., pawn shops or brokers, cashier'scheck issuers, insurance firms, check-cashing locations, payday lending,currency exchanges, microloan organizations, crowd-funding orcrowd-sourcing entities, third-party payment processors, etc.).

Account provider system 130 may include an input/output device 132, atransaction system 134, and a dynamic transaction card system 136.Input/output device 132 may include for example, I/O devices, which maybe configured to provide input and/or output to providing party system130 (e.g., keyboard, mouse, display, speakers, printers, modems, networkcards, etc.). Input/output device 132 also may include antennas, networkinterfaces that may provide or enable wireless and/or wire line digitaland/or analog interface to one or more networks, such as network 110,over one or more network connections, a power source that provides anappropriate alternating current (AC) or direct current (DC) to power oneor more components of account provider system 130, and a bus that allowscommunication among the various components of account provider system130. Input/output device 132 may include a display, which may includefor example output devices, such as a printer, display screen (e.g.,monitor, television, and the like), speakers, projector, and the like.Although not shown, each account provider system 130 may include one ormore encoders and/or decoders, one or more interleavers, one or morecircular buffers, one or more multiplexers and/or de-multiplexers, oneor more permuters and/or depermuters, one or more encryption and/ordecryption units, one or more modulation and/or demodulation units, oneor more arithmetic logic units and/or their constituent parts, and thelike.

Transaction system 134 may include various hardware and softwarecomponents to communicate between a merchant, acquisition system,account provider system, user authentication system 160, and/or a userdevice to process a transaction, such as a user purchase dynamictransaction card system 136 may include various hardware and softwarecomponents, such as data storage (not shown) to store data associatedwith a dynamic transaction card (e.g., card number, account type,account balance, account limits, budget data, recent transactions,pairing data such as time and date of pairing with a mobile device, andthe like) and cardholder data (e.g., cardholder name, address, phonenumber(s), email address, demographic data, and the like).

User authentication system 160 may be separate from or integrated withaccount provider system 130. User authentication system 160 may includevarious hardware and software components to authenticate a user based onuser authentication inputs, which may be gestures or voice prints. Userauthentication system 160 may include data storage that may store dataassociated with a user account (e.g., card number, account type, accountbalance, account limits, budget data, recent transactions, pairing datasuch as time, date, and location of pairing with a mobile device, andthe like) and user account holder data (e.g., account holder name,address, phone number(s), email address, demographic data, and thelike).

User authentication system 160 may utilize software including userauthentication input recognition algorithms, which may include a patternmatching algorithm that will compare the card user performed userauthentication input, which may be a gesture or voiceprint, to thepre-recording of the predetermined user authentication input which maybe saved on EMV™ chip 122, backend 318 system, and/or userauthentication system 160.

Microcontroller 224 may perform voice recognition to determine if EMV™chip 212 and/or a dynamic transaction card 200's magnetic stripe shouldbe activated to activate the dynamic transaction card for usage.

A user device 140 may be any device capable of communicating with atransaction card 120 via, for example, Bluetooth™ technology, NFCtechnology, WiFi Direct technology, and/or the like and execute variousfunctions to transmit and receive account data (e.g., card number,account type, account balance, account limits, budget data, recenttransactions, and/or the like) associated with dynamic transaction card120. For example, user device 140 may be a mobile device such as, aniPhone, iPod, iPad, and/or Apple Watch from Apple® or any other mobiledevice running Apple's iOS operating system, any device running Google'sAndroid® operating system, including, for example, smartphones runningthe Android® operating system and other wearable mobile devices, such asGoogle Glass or Samsung Galaxy Gear Smartwatch, any device runningMicrosoft's Windows® Mobile operating system, and/or any othersmartphone or like device.

User device 140 may be a network-enabled computer. As referred toherein, a network-enabled computer may include, but is not limited to:e.g., any computer device, or communications device including, e.g., aserver, a network appliance, a personal computer (PC), a workstation, amobile device, a phone, a handheld PC, a personal digital assistant(PDA), a thin client, a fat client, an Internet browser, or otherdevice. The one or more network-enabled computers of the example system100 may execute one or more software applications to enable, forexample, network communications.

User device 140 may include for example, an input/output device 142, adynamic transaction card system 144, and a transaction system 146.Input/output device 142 may include, for example, a Bluetooth™ device orchipset with a Bluetooth™ transceiver, a chip, and an antenna. Thetransceiver may transmit and receive information via the antenna and aninterface. The chip may include a microprocessor that stores andprocesses information specific to a dynamic transaction device andprovides device control functionality. Device control functionality mayinclude connection creation, frequency-hopping sequence selection andtiming, power control, security control, polling, packet processing, andthe like. The device control functionality and other Bluetooth™-relatedfunctionality may be supported using a Bluetooth™ API provided by theplatform associated with the user device 140 (e.g., The Androidplatform, the iOS platform). Using a Bluetooth™ API, an applicationstored on a user device 140 (e.g., a banking application, a financialaccount application, etc.) or the device may be able to scan for otherBluetooth™ devices (e.g., a dynamic transaction card 120), query thelocal Bluetooth™ adapter for paired Bluetooth™ devices, establish RFCOMMchannels, connect to other devices through service discovery, transferdata to and from other devices or a transaction card 120, and managemultiple connections. A Bluetooth™ API used in the methods, systems, anddevices described herein may include an API for Bluetooth™ Low Energy(BLE) to provide significantly lower power consumption and allow a userdevice 140 to communicate with BLE devices that have low powerrequirements, such dynamic transaction card 120.

Input/output device 142 may include for example, I/O devices, which maybe configured to provide input and/or output to user device 140 (e.g.,keyboard, mouse, display, speakers, printers, modems, network cards,etc.). Input/output device 142 also may include antennas, networkinterfaces that may provide or enable wireless and/or wire line digitaland/or analog interface to one or more networks, such as network 110,over one or more network connections, a power source that provides anappropriate alternating current (AC) or direct current (DC) to power oneor more components of user device 140, and a bus that allowscommunication among the various components of user device 140.Input/output device 142 may include a display, which may include forexample output devices, such as a printer, display screen (e.g.,monitor, television, and the like), speakers, projector, and the like.Although not shown, each user device 140 may include one or moreencoders and/or decoders, one or more interleavers, one or more circularbuffers, one or more multiplexers and/or de-multiplexers, one or morepermuters and/or depermuters, one or more encryption and/or decryptionunits, one or more modulation and/or demodulation units, one or morearithmetic logic units and/or their constituent parts, and the like.

Input/output device 142 may also include an NFC antenna and secureelement (SE). The SE may be a hardware chip specially designed to betamper proof. In one embodiment, the SE may be used for digitally andphysically secure storage of sensitive data, including transaction carddata, payment data, health records, car key identifiers, etc. The SEmay, for example, store information related to a person, customer,financial institution, or other entity. The SE may store informationrelated to a financial account, such as, for example, transaction carddata (e.g., a credit card number, debit account number, or other accountidentifier, account balance, transaction history, account limits, budgetdata, recent transactions, and/or the like). The SE may include acomputer processor or other computational hardware or software. As oneexample, the secure element may contain the Visa® and MasterCard®applications for PayWave® and PayPass® transactions. A secure elementmay take the form of a universal integrated circuit card (UICC) and/or amicroSD card. A UICC may identify a user to a wireless operator, storecontacts, enable secure connections, and add new applications andservices, such as a transaction system.

Input/output device 142 may enable Industry Standard NFC PaymentTransmission. For example, the input/output device 142 may enable twoloop antennas to form an air-core transformer when placed near oneanother by using magnetic induction. Input/output device 142 may operateat 13.56 MHz or any other acceptable frequency. Also, input/outputdevice 142 may provide for a passive communication mode, where theinitiator device provides a carrier field, permitting answers by thetarget device via modulation of existing fields. Additionally,input/output device 142 also may provide for an active communicationmode by allowing alternate field generation by the initiator and targetdevices.

Input/output device 142 may deactivate the RF field while awaiting data.The attachment may use Miller-type coding with varying modulations,including 100% modulation. The attachment may also use Manchester codingwith varying modulations, including a modulation ratio of 10%.Additionally, the attachment may be capable of receiving andtransmitting data at the same time, as well as checking for potentialcollisions when the transmitted signal and received signal frequenciesdiffer.

Input/output device 142 may be capable of utilizing standardizedtransmission protocols, for example but not by way of limitation,ISO/IEC 14443 A/B, ISO/IEC 18092, MiFare, FeliCa, tag/smartcardemulation, and the like. Also, input/output device 142 may be able toutilize transmission protocols and methods that are developed in thefuture using other frequencies or modes of transmission. Input/outputdevice 142 may also be backwards-compatible with existing techniques,for example RFID. Also, the system may support transmission requirementsto meet new and evolving standards including internet based transmissiontriggered by NFC.

Dynamic transaction card system 144 may work with input/output device142 to generate and receive account data associated with a dynamictransaction card 120. For example, dynamic transaction card system mayinclude various hardware and software components such as a processor anddata storage to store dynamic transaction card data (e.g., cardholdername, address, phone number(s), email address, demographic data, cardnumber, account type, account balance, account limits, budget data,recent transactions and the like).

Transaction system 146 may include various hardware and softwarecomponents, such as data storage and a processor that may work withinput/output device 142 to communicate between a merchant, acquisitionsystem, account provider system, and/or a mobile device to process atransaction, such as a user purchase.

User device 140 may also include various software components tofacilitate the operation of a dynamic transaction card 120. For example,user device 140 may include an operating system such as, for example,the iOS operating system from Apple, the Google Android operatingsystem, and the Windows Mobile operating system from Microsoft. Userdevice 140 may also include, without limitation, software applicationssuch as mobile banking applications and financial institutionapplication to facilitate use of a dynamic transaction card 120, an NFCapplication programming interface, and software to enable touchsensitive displays. Mobile banking applications and/or financialinstitution applications may be combined and/or separate from a dynamictransaction card system 144. Mobile device manufacturers may providesoftware stacks or Application Programming Interfaces (APIs) which allowsoftware applications to be written on top of the software stacks. Forexample, mobile device manufacturers may provide, without limitation, acard emulation API to enable NFC card emulation mode, a logic linkcontrol protocol (LLCP) API for peer-to-peer communication betweenmobile devices, a Bluetooth™ API supporting BLE, and a real-time data(RTD) API and a NFC Data Exchange Format (NDEF) API for reading/writing.

Software applications on user device 140, such as mobile bankingapplications and applications associated with a dynamic transaction card120, may include card on/off features that allow a cardholder associatedwith a user device 140 to enable and disable a transaction card. Forexample, a card holder may use, for example, a mobile bankingapplication stored on a user device 140 to disable and/or enableaccounts associated with a dynamic transaction card 120. A mobilebanking application may include, for example, an application asdisplayed on mobile device 420 in FIG. 4. In this example, a dynamictransaction card 120 may have account data pre-stored on the dynamictransaction card 120 to associate a number of different accounts withthe dynamic transaction card (e.g., debit card, credit card, prepaidcard, and/or the like). If a card holder has a credit accountestablished and desires to establish a debit card associated with thedynamic transaction card 120, the card holder may use a user device 140and/or dynamic transaction card 120 to activate the inactive debitaccount on the dynamic transaction card 120.

For example, software applications on user device 140 may include userapplication 156 which may be a mobile application, which may be utilizedto configure and reset specific user authentication inputs, which may begestures and voiceprints, to be utilized for user authentication inputrecognition, which may be gesture and voice recognition to activatedynamic transaction card 120 by authenticating a card user. Userapplication 156 may record a predetermined user authentication input,which may be a gesture or gesture sequence provided by a card user. Theobserved gesture may include changing the orientation of the card, suchas a rotation of the card 90 degrees clockwise, rotation of the card 180degrees clockwise, a tap, double tap, a series of taps long press,flick, scroll, or pinch of the screen of user device 140, a combinationthereof, and the like. The gesture may also include a signature. Aconnection may be made between user device 140 and dynamic transactioncard 120 (e.g. WiFi, RFID, BLE, and the like) to transmit thepredetermined gesture from user device 140 to dynamic transaction card120, which may securely store the predetermined gesture on EMV™ chip122. A connection may also be made between user device 140 and backend318 system (e.g. WiFi, RFID, BLE, and the like) to transmit thepredetermined gesture from user device 140 to backend 318 system whichmay securely store the predetermined gesture.

User application 156 may record a predetermined voiceprint of a passphrase spoken by a card user. A connection may be made between userdevice 140 and dynamic transaction card 120 (e.g. WiFi, RFID, BLE, andthe like) to transmit the pre-determined voiceprint from user device 140to dynamic transaction card 120, which may securely store thepredetermined voiceprint on EMV™ chip 122. A connection may also be madebetween user device 140 and backend 318 system to transmit thepredetermined voiceprint from user device 140 to backend 318 systemwhich may securely store the predetermined voiceprint.

Merchant system 150 may include, among other components, a Point-of-Sale(PoS) device, an input/output device 152, and an authorization system154. As illustrated in FIG. 8, a PoS device may include a variety ofreaders to read transaction data associated with a transaction takingplace with a merchant. PoS device may include various hardware and/orsoftware components required to conduct and process transaction.Merchant system 150 may also include data storage (not shown) to storetransaction data and/or approval of charges between an cardholder andthe merchant associated with the PoS device.

An input/output device 152 may include, for example, a transceiver,modems, network interfaces, buses, CD-ROM, keyboard, mouse, microphone,camera, touch screen, printers, USB flash drives, speakers, and/or anyother device configured to receive and transmit electronic data.Input/output device 152 may include for example, I/O devices, which maybe configured to provide input and/or output to and/or from merchantsystem 150 (e.g., keyboard, mouse, display, speakers, printers, modems,network cards, etc.). Input/output device 152 also may include antennas,network interfaces that may provide or enable wireless and/or wire linedigital and/or analog interface to one or more networks, such as network110, over one or more network connections, a power source that providesan appropriate alternating current (AC) or direct current (DC) to powerone or more components of merchant system 150, and a bus that allowscommunication among the various components of merchant system 150.Input/output device 152 may include a display, which may include forexample output devices, such as a printer, display screen (e.g.,monitor, television, and the like), speakers, projector, and the like.Although not shown, merchant system 150 may include one or more encodersand/or decoders, one or more interleavers, one or more circular buffers,one or more multiplexers and/or de-multiplexers, one or more permutersand/or depermuters, one or more encryption and/or decryption units, oneor more modulation and/or demodulation units, one or more arithmeticlogic units and/or their constituent parts, and the like. Authorizationsystem 154 may include various software and/or hardware component toenable authorization of a transaction at a merchant system using, forexample, a PoS device.

FIG. 8 depicts an example PoS device 800. PoS device 800 may provide theinterface at what a card holder makes a payment to the merchant inexchange for goods or services. PoS device may be similar to PoS deviceat a merchant system 150. PoS device 800 may include and/or cooperatewith weighing scales, scanners, electronic and manual cash registers,electronic funds transfer at point of sale (EFTPOS) terminals, touchscreens and any other wide variety of hardware and software availablefor use with PoS device 800. PoS device 800 may be a retail point ofsale system and may include a cash register and/or cash register-likecomputer components to enable purchase transactions. PoS device 800 alsomay be a hospitality point of sale system and include computerizedsystems incorporating registers, computers and peripheral equipment,usually on a computer network to be used in restaurant, hair salons,hotels or the like. PoS device 800 may be a wireless point of saledevice similar to a PoS device described herein or, for example a tabletcomputer that is configured to operate as a PoS device, including forexample, software to cause the tablet computer to execute point of salefunctionality and a card reader such as for example the Capital One®SparkPay card reader, the Square® reader, Intuit's® GoPayment reader, orthe like. PoS device 800 also may be a cloud-based point of sale systemthat can be deployed as software as a service, which can be accesseddirectly from the Internet using, for example, an Internet browser.

Referring to FIG. 8, an example PoS device 800 is shown. PoS device 800may include a controller 802, a reader interface 804, a data interface806, a smartcard and/or EMV™ chip reader 808, a magnetic stripe reader810, a near-field communications (NFC) reader 812, a power manager 814,a keypad 816, an audio interface 818, a touchscreen/di splay controller820, and a display 822. Also, PoS device 800 may be coupled with,integrated into or otherwise connected with a cash register/retailenterprise system 824.

In various embodiments, Controller 802 may be any controller orprocessor capable of controlling the operations of PoS device 800. Forexample, controller 802 may be a Intel® 2nd Generation Core™ i3 or i5 orPentium™ G850 processor or the like. Controller 802 also may be acontroller included in a personal computer, smartphone device, tablet PCor the like.

Reader interface 804 may provide an interface between the various readerdevices associated with PoS device 800 and PoS device 800. For example,reader interface 804 may provide an interface between smartcard and/orEMV™ chip reader 808, magnetic stripe reader 810, NFC reader 812 andcontroller 802. In various embodiments, reader interface 804 may be awired interface such as a USB, RS232 or RS485 interface and the like.Reader interface 804 also may be a wireless interface and implementtechnologies such as Bluetooth™, the 802.11(x) wireless specificationsand the like. Reader interface 804 may enable communication ofinformation read by the various reader devices from the various readerdevices to PoS device 800 to enable transactions. For example, readerinterface 804 may enable communication of a credit or debit card numberread by a reader device from that device to PoS device 800. In variousembodiments, reader interface 804 may interface between PoS device 800and other devices that do not necessarily “read” information but insteadreceive information from other devices.

Data interface 806 may allow PoS device 800 to pass communicate datathroughout PoS device and with other devices including, for example,cash register/retail enterprise system 824. Data interface 806 mayenable PoS device 800 to integrate with various customer resourcemanagement (CRM) and/or enterprise resource management (ERP) systems.Data interface 806 may include hardware, firmware and software that makeaspects of data interface 806 a wired interface. Data interface 806 alsomay include hardware, firmware and software that make aspects of datainterface 806 a wireless interface. In various embodiments, datainterface 806 also enables communication between PoS device otherdevices.

Smartcard and/or EMV™ chip reader 808 may be any electronic data inputdevice that reads data from a smart card (e.g. a transaction card asdescribed herein) and/or EMV™ chip. Smartcard and/or EMV™ chip reader808 may be capable of supplying an integrated circuit (e.g., EMV™ chip)on the transaction card with electricity and communicating with thetransaction card via protocols, thereby enabling read and writefunctions. In various embodiments, smartcard and/or EMV™ chip reader 808may enable reading from contact or contactless transaction cards.Smartcard and/or EMV™ chip reader 808 also may communicate usingstandard protocols including ISO/IEC 7816, ISO/IEC 14443 and/or the likeor proprietary protocols.

Magnetic stripe reader 810 may be any electronic data input device thatreads data from a magnetic stripe on a credit or debit card, forexample. In various embodiments, magnetic stripe reader 810 may includea magnetic reading head capable of reading information from a magneticstripe. Magnetic stripe reader 810 may be capable of reading, forexample, cardholder information from tracks 1, 2, and 3 on magneticcards. In various embodiments, track 1 may be written on a card withcode known as DEC SIXBIT plus odd parity and the information on track 1may be contained in several formats (e.g., format A, which may bereserved for proprietary use of the card issuer; format B; format C-Mwhich may be reserved for us by ANSI subcommittee X3B10; and format N-Z,which may be available for use by individual card issuers). In variousembodiments, track 2 may be written with a 5-bit scheme (4 data bitsplus 1 parity). Track 3 may be unused on the magnetic stripe. In variousembodiments, track 3 transmission channels may be used for transmittingdynamic data packet information to further enable enhanced token-basedpayments.

NFC reader 812 may be any electronic data input device that reads datafrom a NFC device. In an example embodiment, NFC reader 812 may enableIndustry Standard NFC Payment Transmission. For example, the NFC reader812 may communicate with a NFC enabled device to enable two loopantennas to form an air-core transformer when placed near one another byusing magnetic induction. NFC reader 812 may operate at 13.56 MHz or anyother acceptable frequency. Also, NFC reader 812 may enable a passivecommunication mode, where an initiator device provides a carrier field,permitting answers by the target device via modulation of existingfields. Additionally, NFC reader 812 also may enable an activecommunication mode by allowing alternate field generation by theinitiator and target devices.

In various embodiments, NFC reader 812 may deactivate an RF field whileawaiting data. NFC reader 812 may receive communications containingMiller-type coding with varying modulations, including 100% modulation.NFC reader 812 also may receive communications containing Manchestercoding with varying modulations, including a modulation ratio ofapproximately 10%, for example. Additionally, NFC reader 812 may becapable of receiving and transmitting data at the same time, as well aschecking for potential collisions when the transmitted signal andreceived signal frequencies differ.

NFC reader 812 may be capable of utilizing standardized transmissionprotocols, for example but not by way of limitation, ISO/IEC 14443 A/B,ISO/IEC 18092, MiFare, FeliCa, tag/smartcard emulation, and the like.Also, NFC reader 812 may be able to utilize transmission protocols andmethods that are developed in the future using other frequencies ormodes of transmission. NFC reader 812 also may be backwards-compatiblewith existing payment techniques, such as, for example RFID. Also, NFCreader 812 may support transmission requirements to meet new andevolving payment standards including internet based transmissiontriggered by NFC. In various embodiments, NFC reader 812 may utilizeMasterCard's® PayPass and/or Visa's® PayWave and/or American Express'®ExpressPay systems to enable transactions.

Although not shown and described, other input devices and/or readers,such as for example, barcode readers and the like are contemplated.

Power manager 814 may be any microcontroller or integrated circuit thatgoverns power functions of PoS device 800. Power manager 814 mayinclude, for example, firmware, software, memory, a CPU, a CPU,input/output functions, timers to measure intervals of time, as well asanalog to digital converters to measure the voltages of the main energystorage component or power source of PoS device 800. In variousembodiments, Power manager 814 remains active even when PoS device 800is completely shut down, unused, and/or powered by the backup energystorage component. Power manager 814 may be responsible for coordinatingmany functions, including, for example, monitoring power connections andenergy storage component charges, charging batteries when necessary,controlling power to other integrated circuits within PoS device 800and/or other peripherals and/or readers, shutting down unnecessarysystem components when they are left idle, controlling sleep and powerfunctions (on and off), managing the interface for built-in keypad andtrackpads, and/or regulating a real-time clock (RTC).

Keypad 816 may any input device that includes a set of buttons arranged,for example, in a block or pad and may bear digits, symbols and/oralphabetical letters. Keypad 816 may be a hardware-based ormechanical-type keypad and/or implemented in software and displayed on,for example, a screen or touch screen to form a keypad. Keypad 816 mayreceive input from a user that pushed or otherwise activates one or morebuttons on keypad 816 to provide input.

Audio interface 818 may be any device capable of providing audio signalsfrom PoS device 800. For example, audio interface may be a speaker orspeakers that may produce audio signals. In various embodiments, audiointerface 818 may be integrated within PoS device 800. Audio interface818 also may include components that are external to PoS device 800.

Touchscreen/display control 820 may be any device or controller thatcontrols an electronic visual display. Touchscreen/display control 820may allow a user to interact with PoS device 800 through simple ormulti-touch gestures by touching a screen or display (e.g., display822). Touchscreen/display control 820 may be configured to control anynumber of touchscreens, including, for example, resistive touchscreens,surface acoustic wave touchscreens, capacitive touchscreens, surfacecapacitance touchscreens, projected capacitance touchscreens, mutualcapacitance touchscreens, self-capacitance touchscreens, infrared gridtouchscreens, infrared acrylic projection touchscreens, opticaltouchscreens, touchscreens based on dispersive signal technology,acoustic pulse recognition touchscreens, and the like. In variousembodiments, touchscreen/display control 820 may receive inputs from thetouchscreen and process the received inputs. Touchscreen/display control820 also may control the display on PoS device 800, thereby providingthe graphical user interface on a display to a user of PoS device 800.

Display 822 may be any display suitable for a PoS device. For example,display 822 may be a TFT, LCD, LED or other display. Display 822 alsomay be a touchscreen display that for example allows a user to interactwith PoS device 800 through simple or multi-touch gestures by touching ascreen or display (e.g., display 822). Display 822 may include anynumber of touchscreens, including, for example, resistive touchscreens,surface acoustic wave touchscreens, capacitive touchscreens, surfacecapacitance touchscreens, projected capacitance touchscreens, mutualcapacitance touchscreens, self-capacitance touchscreens, infrared gridtouchscreens, infrared acrylic projection touchscreens, opticaltouchscreens, touchscreens based on dispersive signal technology,acoustic pulse recognition touchscreens, and the like. In variousembodiments, 822 may receive inputs from control gestures provided by auser. Display 822 also may display images, thereby providing thegraphical user interface to a user of PoS device 800.

Cash register/retail enterprise system 824 may me any device or devicesthat cooperate with PoS device 800 to process transactions. Cashregister/retail enterprise system 824 may be coupled with othercomponents of PoS device 800 via, for example, a data interface (e.g.,data interface 806) as illustrated in FIG. 8. Cash register/retailenterprise system 824 also may be integrated into PoS device 800.

In various embodiments, cash register/retail enterprise system 824 maybe a cash register. Example cash registers may include, for example,mechanical or electronic devices that calculate and record salestransactions. Cash registers also may include a cash drawer for storingcash and may be capable of printing receipts. Cash registers also may beconnected to a network to enable payment transactions. Cash registersmay include a numerical pad, QWERTY or custom keyboard, touch screeninterface, or a combination of these input methods for a cashier toenter products and fees by hand and access information necessary tocomplete the sale.

In various embodiments, cash register/retail enterprise system 824 maycomprise an retail enterprise system and/or a customer relationshipmanagement system. Retail enterprise system 824 may enable retainenterprises to manage operations and performance across a retailoperation. Retail enterprise system 824 may be a stand-alone applicationin, for example, individual stores, or may be interconnected via anetwork. Retail enterprise system 824 may include various point of salecapabilities, including the ability to, for example, customize andresize transaction screens, work with a “touch screen” graphical userinterface, enter line items, automatically look up price (sales,quantity discount, promotional, price levels), automatically computetax, VAT, look up quantity and item attribute, display item picture,extended description, and sub-descriptions, establish default shippingservices, select shipping carrier and calculate shipping charges byweight/value, support multi-tender transactions, including cash, check,credit card, and debit card, accept food stamps, place transactions onhold and recall, perform voids and returns at POS, access online creditcard authorizations and capture electronic signatures, integrate debitand credit card processing, ensure optional credit card discounts withaddress verification, support mix-and-match pricing structure, discountentire sale or selected items at time of sale, add customer account,track customer information, including total sales, number of visits, andlast visit date. issue store credit, receive payment(s) for individualinvoices, process deposits on orders, search by customer's ship-toaddress, create and process layaway, back orders, work orders, and salesquotes, credit items sold to selected sales reps, view daily sales graphat the PoS, view and print journals from any register, preview, search,and print journals by register, batch, and/or receipt number, print X,Z, and ZZ reports, print receipts, invoices, and pick tickets withlogos/graphics, print kit components on receipt, reprint receipts, enteremployee hours with an integrated time clock function, and/or sell whenthe network/server is down with an offline PoS mode. Retail enterprisesystem 824 also may include inventory control and tracking capabilities,reporting tools, customer management capabilities, employee managementtools, and may integrate with other accounting software.

In various embodiments cash register/retail enterprise system 824 may bea hospitality PoS. In such embodiments, retail enterprise system 824 mayinclude hospitality PoS software (e.g., Aloha PoS Restaurant softwarefrom NCR®, Micros® RES and Symphony software and the like), hospitalitymanagement software, and other hardware and software to facilitatehospitality operations.

FIG. 9 illustrates an example system 900 and method for transactionauthorization. As shown and described in FIG. 9, account holders, suchas account holders associated with a dynamic transaction card similar todynamic transaction card 120 and/or a mobile device similar to userdevice 140 and financial institutions similar to account provider system130 may be connected with a card association network to enable securetransactions, timely payments, and successful withdrawals. System 900may include a cardholder 902, merchant 904, Acquirer 910,Association/Interchange 916, and card issuer 918.

Cardholder 902 may be any account holder, including a credit cardholder, debit card holder, stored value card holder and the like.Cardholder 902 may be similar to the card holder associated with dynamictransaction card 120 and/or user device 140. Cardholder 902 may possessa plastic card or carry a device (e.g., a mobile device) that securelystores card credentials and is capable of transmitting the cardcredentials to, for example, a PoS terminal (e.g., terminal 906) and/oran input/output device. Cardholder 902 may interact with a merchantand/or a providing party (e.g., merchant 904) by presenting atransaction card (e.g., dynamic transaction card 120) or cardcredentials to a terminal (e.g., terminal 906).

Merchant 904 may be any merchant that accepts payment from a cardholder902 in exchange for goods, for example. Merchant 904 may be anyretailer, service provider, business entity, or individual that acceptspayments. Merchant 904 may include software, firmware and hardware foraccepting and/or processing payments. For example, as illustrated inFIG. 9, merchant 904 may include a terminal 906 and a payment gateway908. Terminal 906 and payment gateway 908 may comprise the physical orvirtual device(s) used by merchant 904 to communicate information tofront-end processor 912 of acquirer 910. Terminal 906 may be similar toa PoS system. Terminal 906 may include an EMV™ card reader to interactwith a dynamic transaction card. In various embodiments, payment gateway908 may be an e-commerce application service provider service thatauthorizes payments for merchants. As such, payment gateway 908 may be avirtual equivalent of a PoS terminal and interface with, for example, abilling system of merchant 904 and pass data to front-end processor 912of acquirer 910.

Acquirer 910 may be, for example, a financial institution or bank thatholds the contract for providing payment processing services to merchant904. Merchant 904 may have a merchant account that may serve as acontract under which Acquirer 910 may extend a line of credit to amerchant who wishes to accept, for example, credit card transactions. Asshown in FIG. 9, Acquirer 910 may be associated with front-end processor912 and back-end processor 914.

In various examples, front-end processor 912 may be a platform that cardterminal 906 and/or payment gateway 908 communicate with when approvinga transaction. Front-end processor 912 may include hardware, firmware,and software to process transactions. Front-end processor 912 may beresponsible for the authorization and capture portion of credit cardtransaction. Front-end processor 912 also may include additionalfront-end platform interconnections to support, for example, ACH anddebit transactions.

Backend processor 914 may be a platform that takes captured transactionsfrom front-end processor 912 and settles them through an Interchangesystem (e.g., association/interchange 916). Back-end processor 914 maygenerate, for example, daily ACH files for merchant settlement. Back-endprocessor 914 also may handle chargeback handling, retrieval request andmonthly statements.

Association/interchange 916 may be the consumer payment system whosemembers are the financial institutions that issue payment cards and/orsign merchant to accept payment cards. Example associations/interchanges916 may include, Visa®, MasterCard®, and American Express®.Association/interchange 916 may include one or more computer systems andnetworks to process transactions.

Issuer 918 may be a financial institution that issues payment cards andmaintains a contract with cardholders for repayment. In variousembodiments, issuer 918 may issue credit, debit, and/or stored valuecards, for example. Example issuers may include, Capital One®, Bank ofAmerica®, Citibank®, Sun Trust®, and the like.

In various embodiments, processing a payment card transaction mayinvolve two stages: (1) authorization and (2) clearing and settlement.Authorization may refer to an electronic request that is sent throughvarious parties to either approve or decline the transaction. Clearingand Settlement may refer to settlement of the parties' settle accountsto enable the parties to get paid.

During authorization, cardholder 902 may present payment card, such asdynamic transaction card 120, as payment (901A) at merchant 904 PoSterminal 906, for example. Merchant 904 may enter card into a physicalPoS terminal 906 (e.g., an EMV™ terminal) or submit a credit cardtransaction to a payment gateway 908 on behalf of withdrawing party 902via secure connection from a Web site, retail location, or a wirelessdevice.

Payment gateway 908 may receive the secure transaction information(903A) and may pass the secure transaction information (905A) via asecure connection to the merchant acquirer's 910 front-end processor912.

Front-end processor 912 may submit the transaction (907A) toassociation/interchange 916 (e.g., a network of financial entities thatcommunicate to manage the processing, clearing and settlement of creditcard transactions). Association/interchange 916 may route thetransaction (909A) to the customer's Issuer 918. Issuer 918 may approveor decline the transaction and passes the transaction results back(911A) through association/interchange 916. Association/interchange thenmay relay the transaction results (913A) to front-end processor 912.

Front-end processor 912 may relay the transaction results (915A) back tothe payment gateway 908 and/or terminal 906. Payment gateway 908 maystore the transaction results and sends them to merchant 904. Merchant904 may receive the authorization response and complete the transactionaccordingly.

During settlement, merchant 904 may deposit the transaction receipt(921S) with acquirer 910 via, for example, a settlement batch. Capturedauthorizations may be passed (923S) from front-end processor 912 to theback-end processor 914 for settlement. Back-end processor may generateACH files for merchant settlement. Acquirer may submit settlement files(925S, 927S) to Issuer 918 for reimbursement via association/interchange916. Issuer 918 may post the transaction and/or withdrawal and paymerchant 904 (929S, 931S, 933S).

FIG. 2 depicts an example dynamic transaction card 200. As shown in FIG.2, dynamic transaction card 200 may include a top output layer 202. Thetop output layer may be a film covering, a plastic covering, and/or thelike. The top output layer 202 may be constructed of scratch-resistantand/or scratch-proof materials. Materials that may be used as a topouter layer 202 may include polyvinyl chloride (PVC), polylactic acid(PLA), acrylonitrile butadiene styrene (ABS), polyethylene terephthalate(PET), Polyethylene terephthalate glycol-modified (PET-G), polyesterfilm or plastic sheet (e.g., Mylar), polycarbonate (PC), and/or thelike. A dynamic transaction card 200 may further include a topprotective layer 204, such as a clear scratch-resistant coating and/orscratch-proof material to protect the underlying components. Forexample, various scratch-resistant materials include materials coatedwith a scratch resistant chemical coating, such as a UV curable chemicalcoating. Scratch-proof materials may include a mineral glass, a sapphireglass, thin film alloys, ITO, ZnO, PVC, PET, BoPET (e.g., Mylar),polyvinylidene fluoride (e.g., Kynar), polyvinylidene difluoride, PCand/or PET-G.

A dynamic transaction card may include a potting 206 or filler epoxyaround the electrical components to provide strength and/or waterresistance. A potting 206 may include a light guide, which may beconstructed of optical grade materials such as acrylic, resin,polycarbonate, epoxies, and/or glass. Potting 206 may also includeinjection molding, such as over molding and/or multi-shot to encapsulatethe components of card 200. For example, injection molding may includeABS, thermoplastic elastomers (TPE), thermoplastic vulcanizate (TPV),thermoplastic polyurethane (TPU), PET, polycarbonates (PC), coldlamination of the outer films to the body of the card using thermoactiveadhesives, hot lamination of the outer films to the body of the cardusing thermoactive adhesives, and/or silicone. A dynamic transactioncard 200 may further include a Java Applet 208 and Java Appletintegration 210. Although a Java Applet 208 is used through thespecification, any other similar type of code application may be used.Moreover, although Java Applet integration 210 is used throughout thisspecification, any type of interface may be used to allow themicrocontroller to interact with the EMV™ chip. A Java Applet 208 mayinclude code that executes payments, such as payment made using an EMV™chip. A Java Applet 208 may include account-provider specific code toexecute display functionality specific to the account provider. JavaApplet integration 210 may include coded interfaces to allow themicrocontroller to interact with the EMV™ chip 212.

By way of example, EMV™ chip 212 and/or dynamic transaction card 200'smagnetic stripe may be activated to activate dynamic transaction card200 via a sensor 214, which may include any type of sensor describedherein. For example, EMV™ chip 212 and/or a dynamic transaction card'smagnetic stripe may be activated via a touch sensor, where a user isrequired to perform a predetermined user authentication input, which maybe a gesture, such as tapping a location on dynamic transaction card 200a specific number of times and/or for a specific length of time (e.g.,double tap, triple tap, one long tap followed by one short tap, acombination thereof, and/or the like). The user authentication input,which may be a gesture may also be incorporated with manifestations onthe display of the card. For example, if the card lights up three times,the predetermined gesture may require a user to tap three times. EMV™chip 212 and/or a dynamic transaction card 200's magnetic stripe mayalso be activated via an accelerometer, motion sensor, or gyroscope thatdetects the motion and changes in orientation of dynamic transactioncard 200, where a user is required to perform a predetermined gesturesuch as rotating the card 90 degrees clockwise or rotating the card 180degrees counterclockwise. In response to the received sensor input,microcontroller 224 may perform gesture recognition to determine if EMV™chip 212 and/or a dynamic transaction card 200's magnetic stripe shouldbe activated to activate the dynamic transaction card for usage.Microcontroller may utilize software including gesture recognitionalgorithms, which may include a pattern matching algorithm that willcompare the card user performed gesture to the pre-recording of thepredetermined gesture which may be saved on EMV™ chip 122 or backend 318system.

EMV™ chip 212 and/or a dynamic transaction card 200's magnetic stripemay also be activated via a microphone that detects sound, where a useris required to speak a predetermined pass phrase and the microphonedetects the associated voiceprint. In response to the receivedmicrophone input, an analog portion of the raw data of the voiceprintmay be transmitted to microcontroller 224. Digital data that may beextracted from the voiceprint may be transmitted to the microcontroller224 bus for data transfer. Microcontroller 224 may perform voicerecognition to determine if EMV™ chip 212 and/or a dynamic transactioncard 200's magnetic stripe should be activated to activate the dynamictransaction card for usage. Microcontroller may utilize softwareincluding a voice recognition algorithm, which may include a patternmatching algorithm that will compare the user spoken voiceprint to thepre-recording of the predetermined voiceprint which may be saved on EMV™chip 122 or backend 318 system. When multiple users use the same dynamictransaction card, different user authentication inputs, which may begestures and voiceprints associated with each user may be utilized toprovide a simple tracking of dynamic transaction card usage.

An EMV™ chip 212 may include a number of contacts that may interact withand/or be connected to a terminal configured to read data stored on aprocessor of an EMV™ chip 212. During an EMV™ transaction, applicationcryptograms may be used to send and receive data packets between thedynamic transaction card 200 and a terminal, such as a merchantterminal, which may be similar to a terminal included at a merchant 150.For example, data packets may include user authentication informationwhich an acquisition system and/or issuing financial institution may useto authenticate a transaction card 200 during a transaction. Variouscryptographic protocols and/or methods may be used in this datatransmission and reception process. Moreover, during a transactionissuing financial institutions and/or acquisition systems may returnscript commands to the EMV™ chip 212 via a terminal. These scriptcommands and/or data packets may be transmitted between parties over anetwork. Script commands may be used, for example, to blocktransactions, change transaction data stored on the EMV™ chip (e.g.,transaction history, account limits, account balance, and/or the like).Offline data authentication may also take place using, for examplepublic key cryptography to perform payment data authentication. Forexample, offline data authentication may use Static Data Authentication(SDA), Dynamic Data Authentication (DDA), and/or Combined DataAuthentication (CDA).

Dynamic transaction card 200 may also include one or more sensors 214 toreceive input. Sensors 214 may include an activation sensor and/or anoperation sensor, which may be combined and/or separate. An activationsensor may activate the dynamic transaction card 214 and an operationsensor may instruct the dynamic transaction card 200 to perform anaction based on the received input. An activation sensor may require asecurity input, such as a biometric input (e.g., fingerprint, eye scan,gesture recognition, voice recognition, and/or the like), inputindicative of a paired mobile device (e.g., BLE and/or Bluetooth™pairing), input indicative of a password (e.g., a password received viaa sensor on the dynamic transaction card and/or a password received on apaired mobile device), input indicative of a signature (e.g. a signaturereceived via a sensor on the dynamic transaction card and/or a signaturereceived on a paired mobile device, and/or the like. An operation sensormay change a display 216 based on received input, conduct a transactionvia, for example an EMV™ chip 212 and/or contactless paymenttechnologies based on received input, attempt a pairing of a card 200and a mobile device, and/or the like.

By way of example, a sensor 214 may include a capacitive touch sensor, apiezoelectric sensor, an inductive sensor, load cells, a light sensor, atemperature sensor, a resistive touchscreen, including for example ananalogue matrix real (AMR) sensors, fingerprint sensor and/or the like.Sensors 214 may include accelerometers, gyroscopes, motion sensors,and/or photosensors to detect motion input. Sensors 214 may includemicrophones to detect sound. Although the sensor 214 is depicted at aparticular spot in the transaction card 200, a sensor 214 may be placedat any portion of the card to detect, for example, touch, light, heat,energy, sound and/or the like. For example, a sensor may be placedaround the outer edges of a dynamic transaction card 200 or at any spotwithin the dynamic transaction card 200. Sensor 214 also may include theentire exterior surface of transaction card 200.

A display 216 may be provided within the transaction card 200. Althoughthe display as shown includes, for example, a dot matrix display, anumber of other display options may be included in the transaction card200. For example, lighting, such as LED lighting, OLED lighting, electroluminescent (EL) displays, and/or the like, may be used as displaycomponents. Display components may also include electronic paper,Mirasol, TF LCD, Quantum Dot Display, and/or the like. Where lighting isused, various lighting technologies may be used to create a display thatindicates a number of things to a cardholder. For example, edge lightingmay be used to create a specific visual component in the display. Anumber of LED or OLED lights may be used to illuminate various portionsof the display in order to output information to a card holder.

By way of example, a display 216 may be illuminated using a particularcolor to relay to the cardholder balance information of an accountassociated with a transaction card, such as an RGB LED matrix paneland/or RGB LED displays. A red light display may indicate that theaccount balance is within a first predetermined dollar amount or a firstpredetermined percentage of the total spending limit, a particularbudget, a particular budget category, and/or the like. A yellow lightdisplay may indicate that the account balance is within a secondpredetermined dollar amount or a second predetermined percentage of thetotal spending limit, a particular budget, a particular budget category,and/or the like. A green light display may indicate that the accountbalance is within a third predetermined dollar amount or a thirdpredetermined percentage of the total spending limit, a particularbudget, a particular budget category, and/or the like. Various colorsand or number of categories may be used to output this information to acardholder. A display 216 may include other display component, such as,for example, LCD technology, ePaper technology (e.g., e-ink), vacuumflorescent display technology, and/or the like.

By way of example, a display 216 may include a number of LED or OLEDlights and/or light pipes that may be lit in a particular pattern toindicate transaction and/or account information. For example, a display216 may include a circle, semicircle, or other shape of LED or OLEDlighting and/or light pips, where the number of lights illuminatedindicates a dollar amount or a percentage of the total spending limit, aparticular budget, a particular budget category, and/or the like.

By way of example, a display 216 may be activated via a sensor 214,which may include any type of sensor described herein. For example, adisplay may be activated via a touch sensor, where a user is required totap a location on dynamic transaction card 200 a specific number oftimes and/or for a specific length of time (e.g., double tap, tripletap, one long tap followed by one short tap, and/or the like). Inresponse to the received sensor input, a display 216 may be activated todisplay particular data, such as data associated with a transactionhistory, account balance, spending limit, budget categories, budgetspending, budget limits, and/or the like. For example, in response to auser double-tapping a sensor point on dynamic transaction card 200, anumber of LED or OLEDs may be illuminated to display the percentage of abudget consumed (e.g., if a budget is $10,000 and a user has spent$3,000, then 3 out of 10 LEDs or OLEDs may be illuminated to illustratethat 30% of the $10,000 budget has been consumed).

A display may be altered and/or modified, for example, depending onwhich account or card is selected to be used. For example, where dynamictransaction card 200 includes a debit account, a first credit account,and a second credit account, display components 216 may reflect the cardnumber, security code, expiration date, and/or other necessary dataindicative of the account (e.g., second credit account) that is beingused to execute a transaction. A display may be altered and/or modifiedwhen, for example, a dynamic transaction card 200 receives new card dataand/or new account data from an account holder's mobile device via awireless connection. For example, where an account has been marked asassociated with fraudulent activity, an account holder and/or issuingfinancial institution may deactivate the card associated with theaccount and issue a new card. Accordingly, new card data may betransmitted from the issuing financial institution to, for example, anaccount holder's mobile device via a network, and then from an accountholder's mobile device to dynamic transaction card 200 via a wirelessconnection. A display may also be altered and/or modified when dynamictransaction card 200 activates a new account. For example, when anaccount holder applies for a new account (e.g., a new credit cardaccount, a new checking account, and/or the like), if approved, newaccount data may be transmitted to dynamic transaction card 200. Newaccount data may be received at an account holder's mobile device froman issuing financial institution via a network (e.g., using a mobileapplication, mobile optimized website, and/or the like). New accountdata may then be transmitted from an account holder's mobile device todynamic transaction card 200 via a wireless connection (e.g., BLE, RFID,NFC, WiFi, and/or the like) or a contact connection (e.g., using aterminal in contact with an EMV™ processor and/or other microchip).

As described herein, card 200 may be fully or partially pre-loaded withaccount and/or card data. For example, an applet and placeholder data(or actual data) may be stored within dynamic transaction card 200.Accordingly, when an account holder wishes to activate a new account(e.g., account holder who maintains a first credit account may wish toapply for a second credit account), the new account data and/oractivation signal may be received from an account holder's mobile devicevia a wireless connection or a contact connection (e.g., using aterminal in contact with an EMV™ processor and/or other microchip) and anew account and/or card may be activated and able to be displayed ondynamic transaction card 200.

A dynamic transaction card 200 may include a display driver 218 thattranslates instructions from a microcontroller 224 into display imagesto be displayed using display components 216. A display driver 218 mayinclude an integrated circuit (IC), a state machine, and/or the likethat provides an interface function between the display and themicrocontroller 224. A display driver 218 may include memory (e.g., RAM,Flash, ROM, and/or the like) and/or firmware that includes font displaydata.

A dynamic transaction card 200 may include firmware 220 and/or abootloader 222. A bootloader 222 may include code to be executed as adynamic transaction card 200 is activated and before any operatingsystem, firmware, or other code is executed on the dynamic transactioncard 200. A bootloader may be activated via a sensor 214 and energystorage component 228 of the dynamic transaction card 200. Bootloader222 may be activated and/or load an application and/or program upondetection that card 200 has been inserted into a terminal, charger,and/or the like. Bootloader 222 may be activated using only onetechnique described herein, using multiple techniques described herein,and/or using a card holder or card provider selected technique(s)described herein. Bootloader 222 may only be active during a shortinterval after the card 200 powers up. Card 200 may also be activatedusing program code that may be flashed directly to a microprocessor suchas microcontroller 224, EMV™ processor 212, and/or the like. Card 200may not use a bootloader 222 but instead may cycle between a sleep stateand an active state using program code and/or memory.

A dynamic transaction card 200 may include a microcontroller 224 and anantenna 226. Antenna 226 may include, for example, a loop antenna, afractal antenna, and/or the like. Antenna 226 may transmit to andreceive signals from a mobile device, such as user device 140, toconduct transactions and display data as described throughout thespecification. Microcontroller 224 may communicate with EMV™ chip 212,Java Applet 208, Java Applet integration 210, sensor(s) 214, powermanagement 230, antenna 226, energy storage component 228, display 216,display driver 218, firmware 220, bootloader 222, and/or any othercomponent of dynamic transaction card 200. Microcontroller 224 maycontrol the card operations to conduct transactions and/or display dataas described throughout this specification.

Dynamic transaction card 200 may include an energy storage component228. Although energy storage component is depicted as a singlecomponent, energy storage component 228 may include a series of energystorage components. By way of example, energy storage component 228 mayinclude a lithium polymer battery, a lithium-metal battery,lithium-ceramic battery, and/or any other type of battery. Energystorage component 228 may be constructed out of rigid materials,semiflexible materials, and/or flexible materials. Energy storagecomponent 228 may provide power to card components contained withindynamic transaction card 200. Energy storage component 228 may be acombine, for example, a battery/potting component to support dynamictransaction card 200.

Dynamic transaction card 200 may include a power management component230 that may manage the charging and discharging of energy storagecomponent 228. Power management component 230 may convert voltage to apredetermined level in order to operate dynamic transaction card 200 asdiscussed throughout the specification. Power management component 230and/or energy storage 228 may include, for example, solar power cells toconvert solar energy into an electrical current within a solar panel.Power management component 230 and/or energy storage component 228 mayinclude connections to sensors 214 to receive input and activate dynamictransaction card 200 (e.g., motion input, thermal input, manual input,touch input, and/or the like).

A flexible printed circuit board (PCB) 232 may be included in dynamictransaction card 200. A flexible PCB 232 may include a PCB mounted in aflexible plastic substrate, such as for example, a polyimide, polyetherether ketone, and/or a transparent conductive polyester film. A flexiblePCB 232 may be printed, using, for example screen printing, 3D printing,and/or the like, to arrange circuits on a material, such as polyester.Flexible PCB may include electronic components and connections thatpower dynamic transaction card 200. Flexible PCB 232 may control and/orprovide integration between the components of card 200. For example,flexible PCB 232 mechanically supports and electronically connects theelectronic components of card 200 using, for example, conductive tracks,pads, and/or other features. PCB 232 may be combined with an energycomponent (e.g., battery component, power component, etc.) as describedin U.S. Patent Application No. 62/266,324, the entire content of whichare incorporated herein by reference. A flexible PCB may also provideantenna support. A flexible printed circuit (FPC) may be used in placeof or in conjunction with flexible PCB 232. FPC 232 may be fabricatedwith photolithographic technology, such as light exposure of a filmmaterial laminated to substrate and/or conductive layers. FPC 232 may beprinted, silkscreened, and/or the like. FPC 232 may be used as astructural member for the electronic components of card 200 and/or forthe card system as a whole 200. Dynamic transaction card 200 may includea chassis 234 as a frame or supporting structure. Chassis 234 may be amount for a flexible PCB 232 and may be constructed out of flexible orsemi-flexible material as well. Chassis 234 may be constructed out of anumber of materials, including but not limited to, PVC, PC, ABS,styrene, polycarbonate, polyester, PET, any material that is easilymolded, deposited, or laser cut (e.g., organic or inorganic materialsuch as paper, plastic, and/or engineered ceramics), and/or the like.Chassis 234 may be constructed out of a conductive material. Chassis 234may increase the rigidity of dynamic transaction card 200 to preventdamage. Chassis 234 may also be used to detect if dynamic transactioncard 200 is being held by including sensors 214 around chassis 234.Where chassis 234 is constructed out of a conductive material, adielectric constant of chassis 234 and/or card 200 may be monitored todetect handling of card 200. A chassis 234 may be used to detect thehandling of card 200 via a strain gauge. Chassis 234 may be includedwithin or separate from a card backing 236. Card backing 236 may includea magnetic stripe that may be read using a magnetic stripe reader. Amagnetic stripe may store tracks of data that are used to conduct atransaction using a dynamic transaction card 200. The tracks of data mayinclude a first track capable of storing alphanumeric characters as wellas symbols (e.g., ?, !, &, #, and/or the like), such as account numbers,account holder name, expiration data, security data, and/or otheraccount and/or card related data. The tracks of data may include asecond track capable of storing numeric characters such as accountnumbers, expiration data, security data, and/or other account and/orcard related data. The tracks of data may include a third track of datacapable of storing numeric characters such as an account number, a PIN,a country code, a currency code, an authorization amount, a balanceamount, and/or other account and/or card related data.

A magnetic stripe may be dynamically altered. For example, a dynamictransaction card 200 that is paired to a mobile device via, for example,Bluetooth™, BLE, RFID, WiFi Direct and/or other wireless technologies,may receive new track data. The new track data may be unformatted,encrypted, encoded, and/or the like when the new track data istransmitted from the mobile device to the dynamic transaction card 200.Upon receipt of the new track data, the new track data may be routed toa microprocessor, such the processor of EMV™ chip 212 and/ormicrocontroller 224. EMV™ chip 212 and/or microcontroller 224 mayconvert, decrypt, and/or decode the received new track data to ensurecompliance with any standards. Once decrypted, decoded, and/orformatted, the new track data may be save on the tracks of the magneticstripe. The magnetic stripe may be deleted and then the new track datamay be recorded onto the tracks. In this manner, track data stored on amagnetic stripe may be altered at any time upon pairing a dynamictransaction card 200 with a mobile device.

Card backing 236 may be made of similar material to that of the outputlayer 202 and/or the top protective layer 204. Card backing 236 may bemade out of a plastic material.

Although the components of dynamic transaction card 200 are illustratedin a particular fashion, these components may be combined and or placedthroughout a dynamic transaction card 200 in any manner, such as thosedepicted in, for example, FIG. 7.

For example, FIG. 7 illustrates a dynamic transaction card having anoutput layer 702 which may be similar to output layer 202; an outerprotective layer 704 which may be similar to outer protective layer 204;potting 706 which may be similar to potting 206; Java Applets 708 whichmay be similar to Java Applets 208; Java Applet integration 710 whichmay be similar to Java Applet integration 210; an EMV™ chip 712 whichmay be similar to EMV™ chip 212; a sensor 714 which may be similar tosensor 214; display 716 which may be similar to display 216; displaydriver 718 which may be similar to display driver 718; firmware 720which may be similar to firmware 220; bootloader 722 which may besimilar to bootloader 222; microcontroller 724 which may be similar tomicrocontroller 224; antenna 726 which may be similar to antenna 226;energy storage component 728 which may be similar to energy storagecomponent 228; power management 730 which may be similar to powermanagement 230; a flexible PCB 732 which may be similar to flexible PCB232; chassis 734 which may be similar to chassis 234; and/or cardbacking 736 which may be similar to card backing 236.

FIG. 3 illustrates a system associated with the use of a dynamictransaction card. The example system 300 in FIG. 3 may enable afinancial institution, for example, to provide network services to itscardholders, and may include providing transaction card data, accountdata, and/or any other data to a mobile device that may in turn providethat data to a dynamic transaction card. For example, referring to FIGS.1 and 3, a financial institution may include a front-end controlleddomain 306, a back-end controlled domain 312, and a backend 318 as partof account provider system 130, a mobile device 302 may include userdevice 140, and a dynamic transaction card may include dynamictransaction card 120. Referring to FIGS. 3 and 9, for example, a dynamictransaction card may be similar to a dynamic transaction card ofcardholder 902; a financial institution may include a front-endcontrolled domain 306, a back-end controlled domain 312, and a backend318 as part of card issuer system 918 and/or association/interchange916; and a mobile device may be similar to a mobile device of cardholder902. The example system 300 also may enable a merchant, for example, toprovide network services to its customers, and may include providingsales, loyalty account data, and/or any other data to a mobile devicethat may in turn provide that data to a dynamic transaction card. Forexample, a mobile device 302 and/or dynamic transaction card mayinteract with a merchant system, such as merchant system 800 of FIG. 8via a reader 808, 810, 812 to send and/or receive data to the merchantsystem, which may interact with a financial institution over a network,where a financial institution may include a front-end controlled domain306, a back-end controlled domain 312, and a backend 318.

As shown in FIG. 3, system 300 may include a mobile device 302, anetwork 304, a front-end controlled domain 306, a back-end controlleddomain 312, and a backend 318. Front-end controlled domain 306 mayinclude one or more load balancers 308 and one or more web servers 310.Back-end controlled domain 312 may include one or more load balancers314 and one or more application servers 316.

Mobile device 302 may be a network-enabled computer. As referred toherein, a network-enabled computer may include, but is not limited to:e.g., any computer device, or communications device including, e.g., aserver, a network appliance, a personal computer (PC), a workstation, amobile device, a phone, a handheld PC, a personal digital assistant(PDA), a thin client, a fat client, an Internet browser, or otherdevice. The one or more network-enabled computers of the example system300 may execute one or more software applications to enable, forexample, network communications.

Mobile device 302 may include an iPhone, iPod, iPad from Apple® or anyother mobile device running Apple's iOS operating system, any devicerunning Google's Android® operating system, including for example,Google's wearable device, Google Glass, any device running Microsoft'sWindows® Mobile operating system, and/or any other smartphone or likewearable mobile device. Mobile device 302 also may be similar to userdevice 140 as shown and described in FIG. 1.

Network 304 may be one or more of a wireless network, a wired network,or any combination of a wireless network and a wired network. Forexample, network 304 may include one or more of a fiber optics network,a passive optical network, a cable network, an Internet network, asatellite network, a wireless LAN, a Global System for MobileCommunication (GSM), a Personal Communication Service (PCS), a PersonalArea Networks, (PAN), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n, and 802.11g or any other wired or wireless networkfor transmitting and receiving a data signal.

In addition, network 304 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (WAN), alocal area network (LAN) or a global network such as the Internet. Also,network 304 may support an Internet network, a wireless communicationnetwork, a cellular network, or the like, or any combination thereof.Network 204 may further include one network, or any number of exampletypes of networks mentioned above, operating as a stand-alone network orin cooperation with each other. Network 304 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively couples. Network 304 may translate to or from otherprotocols to one or more protocols of network devices. Although network304 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 304 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Front-end controlled domain 306 may be implemented to provide securityfor backend 318. Load balancer(s) 308 may distribute workloads acrossmultiple computing resources, such as, for example computers, a computercluster, network links, central processing units or disk drives. Invarious embodiments, load balancer(s) 310 may distribute workloadsacross, for example, web server(s) 316 and/or backend 318 systems. Loadbalancing aims to optimize resource use, maximize throughput, minimizeresponse time, and avoid overload of any one of the resources. Usingmultiple components with load balancing instead of a single componentmay increase reliability through redundancy. Load balancing is usuallyprovided by dedicated software or hardware, such as a multilayer switchor a Domain Name System (DNS) server process.

Load balancer(s) 308 may include software that monitoring the port whereexternal clients, such as, for example, mobile device 302, connect toaccess various services of a financial institution, for example. Loadbalancer(s) 308 may forward requests to one of the application servers316 and/or backend 318 servers, which may then reply to load balancer308. This may allow load balancer(s) 308 to reply to mobile device 302without mobile device 302 ever knowing about the internal separation offunctions. It also may prevent mobile devices from contacting backendservers directly, which may have security benefits by hiding thestructure of the internal network and preventing attacks on backend 318or unrelated services running on other ports, for example.

A variety of scheduling algorithms may be used by load balancer(s) 308to determine which backend server to send a request to. Simplealgorithms may include, for example, random choice or round robin. Loadbalancers 308 also may account for additional factors, such as aserver's reported load, recent response times, up/down status(determined by a monitoring poll of some kind), number of activeconnections, geographic location, capabilities, or how much traffic ithas recently been assigned.

Load balancers 308 may be implemented in hardware and/or software. Loadbalancer(s) 308 may implement numerous features, including, withoutlimitation: asymmetric loading; Priority activation: SSL Offload andAcceleration; Distributed Denial of Service (DDoS) attack protection;HTTP/HTTPS compression; TCP offloading; TCP buffering; direct serverreturn; health checking; HTTP/HTTPS caching; content filtering;HTTP/HTTPS security; priority queuing; rate shaping; content-awareswitching; client authentication; programmatic traffic manipulation;firewall; intrusion prevention systems.

Web server(s) 310 may include hardware (e.g., one or more computers)and/or software (e.g., one or more applications) that deliver webcontent that can be accessed by, for example a client device (e.g.,mobile device 302) through a network (e.g., network 304), such as theInternet. In various examples, web servers, may deliver web pages,relating to, for example, online banking applications and the like, toclients (e.g., mobile device 302). Web server(s) 310 may use, forexample, a hypertext transfer protocol (HTTP/HTTPS or sHTTP) tocommunicate with mobile device 302. The web pages delivered to clientdevice may include, for example, HTML documents, which may includeimages, style sheets and scripts in addition to text content.

A user agent, such as, for example, a web browser, web crawler, ornative mobile application, may initiate communication by making arequest for a specific resource using HTTP/HTTPS and web server 310 mayrespond with the content of that resource or an error message if unableto do so. The resource may be, for example a file on stored on backend318. Web server(s) 310 also may enable or facilitate receiving contentfrom mobile device 302 so mobile device 302 may be able to, for example,submit web forms, including uploading of files.

Web server(s) also may support server-side scripting using, for example,Active Server Pages (ASP), PHP, or other scripting languages.Accordingly, the behavior of web server(s) 310 can be scripted inseparate files, while the actual server software remains unchanged.

Load balancers 314 may be similar to load balancers 308 as describedabove.

Application server(s) 316 may include hardware and/or software that isdedicated to the efficient execution of procedures (e.g., programs,routines, scripts) for supporting its applied applications. Applicationserver(s) 316 may comprise one or more application server frameworks,including, for example, Java application servers (e.g., Java platform,Enterprise Edition (Java EE), the .NET framework from Microsoft®, PHPapplication servers, and the like). The various application serverframeworks may contain a comprehensive service layer model. Also,application server(s) 316 may act as a set of components accessible to,for example, a financial institution, or other entity implementingsystem 300, through an API defined by the platform itself. For Webapplications, these components may be performed in, for example, thesame running environment as web server(s) 310, and application servers316 may support the construction of dynamic pages. Application server(s)316 also may implement services, such as, for example, clustering,fail-over, and load-balancing. In various embodiments, where applicationserver(s) 316 are Java application servers, the web server(s) 316 maybehaves like an extended virtual machine for running applications,transparently handling connections to databases associated with backend318 on one side, and, connections to the Web client (e.g., mobile device302) on the other.

Backend 318 may include hardware and/or software that enables thebackend services of, for example, a financial institution, merchant, orother entity that maintains a distributed system similar to system 300.For example, backend 318 may include, a system of record, online bankingapplications, a rewards platform, a payments platform, a lendingplatform, including the various services associated with, for example,auto and home lending platforms, a statement processing platform, one ormore platforms that provide mobile services, one or more platforms thatprovide online services, a card provisioning platform, a general ledgersystem, and/or a location system, which may include additionalcapabilities, such as transaction card data generation, transactionprocessing, and/or transmission of account and/or transaction data.Backend 318 may be associated with various databases, including accountdatabases that maintain, for example, cardholder information (e.g.,demographic data, credit data, cardholder profile data, and the like),transaction card databases that maintain transaction card data (e.g.,transaction history, account balance, spending limit, budget categories,budget spending, budget limits, and the like), and the like. Backend 318also may be associated with one or more servers that enable the variousservices provided by system 300. Backend 318 may enable a financialinstitution to implement various functions associated with reprogramminga transaction card and/or providing data to a transaction card in orderto provide a dynamic display as shown and described herein.

A dynamic display may be a display that is altered by activating newcard data such as, a new card number, a new security code (e.g., CCVcode), a new expiration date, and/or other card/account data. A dynamicdisplay may be a display that is altered by activating new account data,such as a new account number, a new card number, a new security code, anew expiration date, and/or other card/account data. New account and/ornew card data may be fully pre-loaded, partially pre-loaded, and/orreceived from a wireless connection.

For example, fully pre-loaded data may include a full account number,card number, security code, expiration date, and/or other account datathat is loaded onto a dynamic transaction card (e.g., dynamictransaction card 200, 700) upon personalization at a backend facility.Fully pre-loaded data may also include an associated applet thatinteracts with the account and/or card data to execute transactions,manipulate dynamic displays, and/or perform any of the functionalitydescribed herein. Fully pre-loaded data may be activated upon receivingan activation signal from, for example, an account holder device via awireless connection. A wireless device may receive an activation signalfrom an issuing financial institution via a network connection using,for example, a mobile application and/or mobile-enhanced websiteassociated with the issuing financial institution.

Partially pre-loaded data may include a shell account that includes aplaceholder for each type of data required for a fully-functionalaccount (e.g., account holder data, account number, security code,expiration date, and/or the like). A placeholder may include one or morealphanumeric characters associated with inactive, null, or shellaccounts in a backend system associated with the issuing financialinstitution. Partially pre-loaded data may include an associated appletthat interacts with the account and/or card data to executetransactions, manipulate dynamic displays, and/or perform any of thefunctionality described herein. Partially pre-loaded data may beactivated upon receiving an activation signal and/or new card or newaccount data from, for example, an account holder device via a wirelessconnection or a contact connection (e.g., using a terminal in contactwith an EMV™ processor and/or other microchip). A wireless device mayreceive an activation signal and/or new card or new account data from anissuing financial institution via a network connection using, forexample, a mobile application and/or mobile-enhanced website associatedwith the issuing financial institution.

Data transmitted may be encrypted. Encryption/decryption may occur usinga key that was preloaded onto the dynamic transaction card uponpersonalization at the issuing financial institution and/or a keypreloaded to an EMV™ circuit. Data received may include new accountand/or card data. For example, where partially pre-loaded card and/oraccount data are stored on a dynamic transaction card, new card and/oraccount data may be received from an account holder's mobile device viaa wireless connection (e.g., BLE, NFC, WiFi, and/or the like) or acontact connection (e.g., using a terminal in contact with an EMV™processor and/or other microchip). Data received may include an appletand/or applet data required to execute transactions, manipulate dynamicdisplays, and/or perform any of the functionality described herein.

Also, fully pre-loaded and/or partially pre-loaded data may also includekeys (e.g., public/private key pairs, private key pairs, and/or thelike) that may be used by an EMV™ circuit to execute transactions usingthe EMV™ processor on the card.

FIG. 4 illustrates a system associated with the use of a dynamictransaction card. The example system 400 in FIG. 4 may enable a mobiledevice 420 storing a mobile banking application, for example, to providedata updates to a dynamic transaction card 410 via network 430. Forexample, data received at mobile device 420 may be transmitted todynamic transaction card 410 where it is received via antenna 414. Datamay be received and/or transmitted using, for example a mobile bankingapplication that maintains and/or creates a secure connection with afinancial institution to send and/or receive data related to an accountassociated with the financial institution. For example, a mobile bankingapplication may include send and/or receive data related to a creditaccount, a debit account, a prepaid account, a loyalty account, arewards account, and/or the like. Data may also include track data thatmay be updated upon demand.

Upon activation of dynamic transaction card via, for example, a sensor418, a data request may be transmitted to a mobile device 420 forupdated information, where mobile device 420 may request updated datafrom a financial institution (not shown) as described in FIG. 3. Datareceived at dynamic transaction card 410 may be stored on microchip 412and/or may be displayed via display 416.

For example, FIGS. 5 and 6 illustrate example methods of updating andusing a dynamic transaction card. The method 500 may start at block 502.At block 504, a dynamic transaction card may be activated. A dynamictransaction card may be activated via input received at a sensor on thedynamic transaction card (e.g., an accelerometer, a light sensor, acapacitive touch sensor, a heat sensor, and/or the like), by insertingthe dynamic transaction card into a reader, such as an EMV™ reader wherethe EMV™ reader connects with the dynamic transaction card via an EMV™chip, when the dynamic transaction card is being used in a contactlesspayment transaction (e.g., by received a signal from a PoS terminal thata transaction has been initiated), via an activation signal receivedfrom a mobile device (e.g., a signal received from a mobile device thathas been paired to the dynamic transaction card via, for exampleBluetooth™ or BLE), and/or the like.

At block 506, upon activation, a dynamic transaction card may requestupdated data via, for example, a mobile device, an EMV™ terminal, and/orany computing device capable of communicating with a financialinstitution. A request may be transmitted wirelessly, using Bluetooth™,Bluetooth™ Low Energy (BLE), RFID, WiFi Direct, and/or NFC technologies.A request may be transmitted via contacts, such as EMV™ contacts. Forexample, a request may be processed using the systems described in FIGS.1, 2, 3, 7, 8, and 9. For example, as illustrated in FIG. 3, a mobiledevice 302 may send data to and receive data from a financialinstitution, for example, through a network 304 using a number of loadbalancers 308, 314 a web server 310, an application server 316, and/or abackend server 318. In this manner, data may be securely transmittedbetween a mobile device 302 and a financial institution. Moreover, amobile banking application and/or a financial institution applicationmay provide a secure connection and/or security features (e.g.,cryptographic keys, protocol, hash algorithm, digital signatures,passwords, checksums, updated gesture and voiceprint keys, and/or thelike) to conduct secure communications with a financial institutionbackend and receive updated financial data to transmit, via RFID, BLE,Bluetooth™, NFC, and/or the like, to a dynamic transaction card forstorage and/or display.

At block 508, data updates, such as transaction data, transactionhistory, account balance, account limit, budget category, remainingbudget amount, spending per category, and/or the like may be received atthe dynamic transaction card via an antenna, such as antenna 224, orcontact points of an EMV™ chip, such as EMV™ chip 212. Data updates maybe stored within the dynamic transaction card and recalled on thedynamic transaction card at any time upon activation. For example, adynamic transaction card may store data in storage associated with amicrocontroller such as microcontroller 224, an EMV™ chip such as EMV™chip 212, and or software storage (e.g., firmware and/or an application)such as 220, 208 in the dynamic transaction card.

At block 510 a dynamic transaction card may generate a display accountto the updated data using a display such as display 216, display driversuch as display driver 218, and/or other components of a dynamictransaction card, including, for example, firmware, such as firmware 220and/or applications, such as application 208. For example, a dynamictransaction card with a dot matrix display may generate an alphanumericdisplay indicative of the updated data, such as a balance amount, atransaction amount, a budget amount, a transaction date, account holdername, account number, transaction card number, expiration date, accountholder data, a spending limit, and/or the like. When a dynamictransaction card display includes and LED and/or an OLED display, adynamic transaction card may generate a display pattern with the LEDand/or OLED lights indicative of the updated data.

By way of example, as displayed in FIG. 2, a display may indicate anamount remaining in an account (e.g., $143 left). A display may includea shape, such as a circle, a ring, and/or the like, indicative of anaccount balance, a budget balance, and/or the like where a portion ofthe shape is illuminated to indicate an account balance against anaccount limit. For example, where a spending limit or budgeted amount is$500 and a balance or amount spent is $100, the shape may be illuminatedto indicate 20% of the spending limit or budgeted amount has been spent.In this example, the shape may be illuminated to indicate 80% of thespending limit or budgeted amount has not been spent. In anotherexample, various colors and/or patterns may be illuminated to indicatean amount spent and/or an amount not spent to a card holder (e.g., anLED or OLED patterns and/or colors, edge lighting patterns, and/or thelike).

At block 512, a dynamic transaction card and/or display on a dynamictransaction card may be deactivated. Deactivation may occur after acertain amount of time after activation. Deactivation may occur byreceiving a predetermined input via a sensor. For example, a first inputto a sensor may activate a dynamic transaction card and a second inputto a sensor may deactivate a dynamic transaction card. A predeterminedinput pattern also may deactivate a dynamic transaction card.Deactivation may occur by removing a dynamic transaction card from aterminal. Deactivation may occur when a dynamic transaction card isunpaired from a mobile device. For example, when a dynamic transactioncard is over a predetermined distance from a mobile device, a wirelessconnection (e.g., BLE, Bluetooth™, RFID, NFC, WiFi Direct, and/or thelike) may be lost and the dynamic transaction card and mobile device maybecome unpaired. Deactivation may occur upon receiving an input that amobile device and financial institution have ceased connection. Forexample, when an account holder logs into a mobile banking applicationon a mobile device, the account holder may log out or a connection maytimeout. Once a connection is lost, either via a log out or timeout, amobile device may transmit a signal to a dynamic transaction cardwirelessly via BLE, Bluetooth™, RFID, NFC, WiFi Direct, and/or the liketo deactivate the display on the dynamic transaction card. Upondeactivation, the method 500 may end.

The method 600 may start at block 602. At block 604, a dynamictransaction card may be activated. A dynamic transaction card may bepowered up or activated via input received at a sensor on the dynamictransaction card (e.g., an accelerometer, a light sensor, a capacitivetouch sensor, a heat sensor, and/or the like), by inserting the dynamictransaction card into a reader, such as an EMV™ reader where the EMV™reader connects with the dynamic transaction card via contact points ofan EMV™ chip, when the dynamic transaction card is being used in acontactless payment transaction (e.g., by received a signal from a PoSterminal that a transaction has been initiated), via an activationsignal received from a mobile device (e.g., a signal received from amobile device that has been paired to the dynamic transaction card via,for example Bluetooth™, BLE, NFC, WiFi Direct, RFID, and/or the like),and/or the like.

At block 606, upon activation, a dynamic transaction card may transmit atransaction request to a point-of-sale (PoS) terminal at a merchant,similar to merchant 150. For example, a dynamic transaction card mayinteract with a merchant terminal (e.g., FIG. 9, 906) to initiate atransaction. A dynamic transaction card may communicate wirelessly(e.g., RFID, NFC, BLE, WiFi Direct) or using a contact connection (e.g.,an EMV™ processor connection at a terminal) with a merchant terminal. Toinitiate a transaction, a cardholder may select a specific card to usefor a transaction. For example, a dynamic transaction card may store anumber of different accounts (e.g., debit account, credit account,prepaid card account, gift card account, and/or the like). A dynamictransaction card may also store a specific applet that executes witheach account and an account identifier (AID) associated with the accountand/or applet. Accordingly, a cardholder may select which account to usefor a transaction, either via a dynamic transaction card interface orvia a mobile device application that may communicate wirelessly with adynamic transaction card to relay transaction instructions (e.g., usecredit account, use debit account, and/or the like).

Also, a cardholder may preselect which account to use for specifictransactions by setting up account rules (e.g., use credit account tomaximize rewards, use debit account when credit balance is at apredetermined level, use credit account at a specific merchant type,and/or the like). Account rules may be stored on a dynamic transactioncard and/or an account holder's mobile device (which may then be pushedto a dynamic transaction card at the time a transaction is initiated).

Upon transmitting a transaction request and/or upon receivingtransaction approval, a dynamic transaction card may receive updateddata based on the current transaction at block 608. Updated data mayinclude the transaction amount, an account balance prior to thetransaction, an account balance after transaction approval, an accountnumber, account holder data, budget category, remaining budget amount,spending per category, and/or the like. Data updates may be storedwithin the dynamic transaction card and recalled on the dynamictransaction card at any time upon activation. For example, a request maybe processed using the systems described in FIGS. 1, 2, 3, 7, 8, and 9.For example, as illustrated in FIG. 3, a mobile device 302 may send datato and receive data from a financial institution, for example, through anetwork 304 using a number of load balancers 308, 314 a web server 310,an application server 316, and/or a backend server 318. In this manner,data may be securely transmitted between a mobile device 302 and afinancial institution. Moreover, a mobile banking application and/or afinancial institution application may provide a secure connection and/orsecurity features (e.g., cryptographic keys, protocol, hash algorithm,digital signatures, passwords, checksums, and/or the like) to conductsecure communications with a financial institution backend and receiveupdated financial data to transmit, via RFID, BLE, Bluetooth™, NFC,and/or the like, to a dynamic transaction card for storage and/ordisplay.

At block 610 a dynamic transaction card may generate a display accountto the updated data using a display, display driver, and/or othercomponents of a dynamic transaction card. For example, a dynamictransaction card with a dot matrix display may generate an alphanumericdisplay indicative of the updated data, such as a balance amount, atransaction amount, a budget amount, a transaction date, account holdername, account number, transaction card number, expiration date, accountholder data, a spending limit, and/or the like. When a dynamictransaction card display includes and LED and/or an OLED display, adynamic transaction card may generate a display pattern with the LEDand/or OLED lights indicative of the updated data.

At block 612, a dynamic transaction card may be deactivated.Deactivation may occur after a certain amount of time after activation.Deactivation may occur by receiving a predetermined input via a sensor.For example, a first input to a sensor may activate a dynamictransaction card and a second input to a sensor may deactivate a dynamictransaction card. A predetermined input pattern also may deactivate adynamic transaction card. Deactivation may occur by removing a dynamictransaction card from a terminal. Upon deactivation, the method 600 mayend.

As another example, FIG. 10 illustrates an example method 1000 ofcommunication between a dynamic transaction card and, for example, amobile device. Dynamic transaction card may be similar to, for example,dynamic transaction card 200 or dynamic transaction card 700. Mobiledevice may be similar to, for example, user device 140.

At block 1002, the method may begin. At block 1004, an account holderand/or financial institution may store transaction rules associated witha dynamic transaction card on a mobile device. Transaction rules mayinclude for example, rules pertaining to allowing or denyingtransactions based on a purchase amount, the time of day, the date, theday of the week, the merchant, the geographical location of thetransaction, the type of merchant, and/or the like.

At block 1006, a dynamic transaction card and/or mobile device maydetermine whether a connection exists between a dynamic transaction cardand a mobile device. For example, a connection may be made by pairing adynamic transaction card and a mobile device using NFC, BLE, Bluetooth™,RFID, WiFi Direct, and/or other connection technologies.

When a connection is detected, a mobile device may receive a request forupdated rules from a dynamic transaction card at block 1008. Rules maybe updated on a dynamic transaction card in response to receiving arequest from the dynamic transaction card. In another example, ruleupdates at a dynamic transaction card may occur when a dynamictransaction card requests balance information from a mobile device. Ruleupdates may occur every time a dynamic transaction card is activated orwakes up and receives additional updated information, such as locationinformation, transaction information. and/or the like. Where no requestand/or transmission of updated rules occurs at a mobile device, a mobiledevice may check a connection between a dynamic transaction card and amobile device. (block 1006).

At block 1010, the updated rules may be transmitted from the mobiledevice to the dynamic transaction card via, for example, NFC, BLE,Bluetooth™, RFID, WiFi Direct, and/or other technologies. Updates may betransmitted as a full reset of transaction rules thereby replacing thetransaction rules previously stored on the dynamic transaction card.Updates may be transmitted as the changes between the currenttransaction rules stored on a dynamic transaction card and the updatedtransaction rules stored on a mobile device.

At block 1012, updated transaction rules may be stored in amicrocontroller, microprocessor, and/or other element of a dynamictransaction card and run during a transaction prior to transmitting anydata to an authorization network and/or financial institution. Thismethod is further illustrated in FIG. 11.

For example, FIG. 11 also illustrates a method for communication betweena financial institution, mobile device, and/or dynamic transaction card.For example, a mobile device may communicate with a financialinstitution to transmit and validate a set of transaction rules.

The method 1100 of FIG. 11 may begin at block 1102. At block 1104, acard holder may define a set of transaction rules, such as rules thatdefine when a transaction card may be used in a transaction. A set ofrules may be defined on, for example, an Internet connected deviceand/or a mobile device, such as user device 140, using a mobileapplication and/or a website.

At block 1106, the transaction rules may be transmitted from a mobiledevice and/or Internet connected device to a financial institutionassociated with the transaction card for which transaction rules aredevice, where the backend system of the financial institution may bestored and validated. Upon validation, a financial institution systemmay transmit validated transaction rules to a mobile device associatedwith the transaction card at block 1108. A financial institution systemmay store an association between a transaction card and a mobile device.For example, a financial institution system may store a link between amobile device identifier (e.g., mobile device number, mobile devicecarrier, mobile device application identifier, device UUID, deviceUDID), an account identifier (e.g., account holder name, account holderusername, account number, and/or the like) and a transaction card (e.g.,transaction card identifier, transaction card number, and/or the like).Accordingly, a financial institution, using the information linking amobile device identifier, account identifier, and a transaction card, afinancial institution may transmit validated transaction rules to amobile device that may be paired with the transaction card associatedwith the validated transaction rules.

At block 1106, the transaction rules may be transmitted from a mobiledevice and/or Internet connected device to a financial institutionassociated with the transaction card for which transaction rules aredevice, where the backend system of the financial institution may bestored and validated. Upon validation, a financial institution systemmay transmit validated transaction rules to a mobile device associatedwith the transaction card at block 1108. A financial institution systemmay store an association between a transaction card and a mobile device.For example, a financial institution system may store a link between amobile device identifier (e.g., mobile device number, mobile devicecarrier, mobile device application identifier, device UUID, deviceUDID), an account identifier (e.g., account holder name, account holderusername, account number, and/or the like) and a transaction card (e.g.,transaction card identifier, transaction card number, and/or the like).Accordingly, a financial institution, using the information linking amobile device identifier, account identifier, and a transaction card, afinancial institution may transmit validated transaction rules to amobile device that may be paired with the transaction card associatedwith the validated transaction rules.

At block 1112, the validated transaction rules may be stored on amicrocontroller, microprocessor, and/or other storage on a dynamictransaction card, which may be similar to dynamic transaction card 200and/or dynamic transaction card 700.

At block 1114, a dynamic transaction card may be used in a transaction.For example, a microcontroller, microprocessor, and/or other componentof the dynamic transaction card may receive transaction details byobserving EMV™ traffic at the EMV™ processor/contacts of the dynamictransaction card. A microcontroller, microprocessor and/or other elementof the dynamic transaction card may execute the stored validated rulesto determine if a transaction may occur. For example, a purchase thatdoes not comply with the validated transaction rules may be denied or apurchase that complies with the validated transaction rules may beaffirmed by the rules before any purchase data is transmitted to anauthorization system and/or a financial institution system.

At block 1116, the microcontroller, microprocessor, and/or other elementof the dynamic transaction card that executes the validated transactionrules may transmit the transaction determination to the EMV™ processorvia EMV™ contacts of the dynamic transaction card, which may interactwith a reader at a PoS device to relay the transaction determination tothe PoS device. If the determination is to deny the transaction, the PoSdevice will no longer proceed with the transaction and the method mayend. If the determination is to affirm the transaction, a PoS device maycontinue processing the transaction, which may include, for example,transmitting transaction information to an authorization system and/orfinancial institution system as described herein.

At block 1118, the method may end. Where, in the methods of FIGS. 10 and11, a mobile device and a transaction card are not able to be paired(e.g., the mobile device lacks power, NFC/BLE/Bluetooth™/WiFi Directtechnologies are disabled, and/or the like), a dynamic transaction cardmay detect that no connection exists between the dynamic transactioncard and a mobile device and may instruct a microcontroller,microprocessor, EMV™ processor, and/or other component of the dynamictransaction card to handle transactions without using validated rules onthe dynamic transaction card.

FIGS. 12, 13, and 14 illustrate example configurations and methods ofcommunication and/or connection between a terminal, such as a PoSterminal, and components of a dynamic transaction card, such as an EMV™processor via EMV™ contacts, microprocessor, and/or applet. Using theseexample configurations, data may be transmitted between a terminal, EMV™contacts, EMV™ processor, applet, and/or microprocessor in a securemanner in order to perform the methods described herein. For example, byusing the depicted connections, data may be stored and/or updated in adynamic transaction card. Using the depicted connections, the datastored and/or updated in a dynamic transaction card may be used togenerate a display component on a dynamic transaction card, such as adot matrix display, an LED or OLED display, and/or the like.

For example, as depicted in FIG. 12, the system 1200 may include a PoSterminal 1210 and a dynamic transaction card 1220. Upon connectionbetween a PoS terminal 1210 and a dynamic transaction card 1220, usingfor example EMV™ processor 1230, data may be read and encrypted using aprivate key stored within EMV™ processor 1230. The encrypted data may betransmitted along with plaintext data from a PoS terminal 1210 to anacquirer, a payment network, and/or an issuer where the encrypted datamay be decrypted. The decrypted data may be compared with the plaintextdata at the issuer. The issuer may use the decrypted data to process atransaction being conducted at a PoS terminal 1210. Once a transactionhas been processed at an issuer, a response (e.g., a plaintext response)may be sent from the issuer to a dynamic transaction card via a paymentnetwork, acquirer, and/or PoS terminal 1210.

A response may then be transmitted to an EMV™ processor 1230 on dynamictransaction card 1220. An EMV™ processor 1230 may then transmit data toan applet 1240, which may then be transmitted to a microprocessor 1250.In this manner, the EMV™ processor 1230 may include protocols and/orinterfacing hardware and/or software to communicate with applet 1240,which may then communicate with a microprocessor 1250.

FIG. 13 illustrates a terminal 1310 and dynamic transaction card 1320included in a system 1300. In FIG. 13, an applet 1340 may be incommunication with a terminal 1310, whereby the applet 1340 may act as aconduit between the EMV™ processor 1330 and terminal 1310. In thismanner, the plaintext data responses may be read and processed using theapplet 1340 and/or microprocessor 1350. For example, applet 1340 maypass any received data to microprocessor 1350 where the data may beprocessed according to any method described herein. Microprocessor maythen transmit the processed data to the applet 1340 where the data maybe used to generate and/or change a display.

FIG. 14 illustrates a terminal 1410 and dynamic transaction card 1420included in a system 1400. In FIG. 14, a microprocessor 1450 may be incommunication with a terminal 1410, whereby the microprocessor 1450 mayact as a conduit between the EMV™ processor 1430 and terminal 1410. Inthis manner, the plaintext data responses may be read and processedusing the microprocessor 1450. For example, microprocessor 1450 mayprocess the response data according to any method described herein.Microprocessor 1450 may then transmit the processed data to the applet1440 where the data may be used to generate and/or change a display.

FIG. 15 illustrates a method 1500 for detecting fraud using a dynamictransaction card 200/700 in a transaction. The techniques andtechnologies used to detect fraud in a transaction may be similar tothose described in U.S. patent application Ser. No. 14/977,730, theentire contents of which are incorporated herein by reference. Themethod 1500 may be used in conjunction with existing fraud detectionmethods and/or technologies and/or newly developed fraud detectionmethods and technologies.

The method may begin at block 1502. At block 1504 a dynamic transactioncard, such as card 200 or 700, may be initiated. A dynamic transactioncard may be initiated upon removing a card from a wallet via lightsensors, touch sensors, and/or other types of sensors described herein.Upon initiation, dynamic transaction card may attempt to pair with aknown mobile device, such as an account holders smartphone, at block1506. At block 1508, a determination regarding a connection is storedwithin the dynamic transaction card.

At block 1510, where a connection is not made, a transaction may beinitiated. Upon initiation of a transaction, along with the transactiondata (e.g., merchant identifier, purchase price, and/or the like), dataindicating that no connection was made between the dynamic transactioncard and a mobile device may be included. Upon receiving thisinformation, a backend system may transmit a message to a known mobiledevice associated with the dynamic transaction card. A message mayinclude a notification of a non-pairing transaction, a request forapproval of a non-pairing transaction, and/or the like. A backend systemmay continue to calculate a fraud score based on the non-pairingtransaction alone or in conjunction with additional fraud calculationsalready in place or may wait for a response from the known mobile devicethat received the transmitted message. If the backend system waits for aresponse from the known mobile device, the non-pairing data as well asthe response data may be included with the transaction data to calculatea fraud score for the transaction. This calculation of a fraud score maybe based on any of the following data, either alone, or in conjunctionwith existing fraud calculations: responds data, transaction data,pairing data, and location data.

At block 1512, a fraud score may be calculated for a non-pairingtransaction. A fraud score may be based on a transaction amount, amerchant identifier, as well as, the response data, the non-pairingdata, a distance between a known mobile device and a transactionlocation and/or transaction statistics associated with the accountholder of the dynamic transaction card. Transaction statistics mayinclude, a number of transactions that occur without pairing, apercentage of transactions that occur without pairing, a number oftransactions approved without pairing, a percentage of transactionsapproved without pairing, and/or the like.

At block 1514 a transaction may be approved or denied based on thecalculated fraud score.

At block 1518, where a connection is made, a transaction may beinitiated. Upon initiation of a transaction, along with the transactiondata (e.g., merchant identifier, purchase price, and/or the like), dataindicating that a connection was made between the dynamic transactioncard and a mobile device may be included. At block 1520, a fraud scoremay be calculated based on a successful pairing. A fraud score may bebased on a transaction amount, a merchant identifier, as well as, theresponse data, the non-pairing data, a distance between a known mobiledevice and a transaction location and/or transaction statisticsassociated with the account holder of the dynamic transaction card.Transaction statistics may include, a number of transactions that occurwithout pairing, a percentage of transactions that occur withoutpairing, a number of transactions approved without pairing, a percentageof transactions approved without pairing, and/or the like.

At block 1522, a transaction may be approved or denied based on thecalculated fraud score.

At blocks 1516 and/or 1524, the method 1500 may end.

FIG. 16 illustrates a method 1600 used after a fraud detection, eitherusing methods disclosed herein or existing fraud detection methods, toautomatically activate new card data on a dynamic transaction card(e.g., dynamic transaction card 200, dynamic transaction card 700).

The method 1600 may begin at block 1602 when a backend financialinstitution system detects a fraudulent transaction. Once a fraudulenttransaction is detected at a backend financial institution system, anotification may be transmitted to the account data storage to block theaccount associated with the fraudulent transaction from being used(block 1606). At block 1604, a backend financial institution system maygenerate new card data (e.g., a new card activation signal, a new cardnumber, a new security code, a new expiration date, and/or the like). Atblock 1608, a backend financial system may push or transmit the new carddata to an account data storage to associate the new card data with theaccount that was marked as associated with a fraudulent transaction.

At block 1610, a backend financial institution system may transmit(e.g., push) a notification to the mobile device of the account holderassociated with the fraud detection and new card data. A notificationmay include data indicating that fraud has been detected, dataindicating that the account data currently stored on a dynamictransaction card is no longer active, and/or data indicating that newcard data must be requested. At block 1612, in response to receiving anotification, an account holder associated with the mobile device mayrequest new card data (e.g., pull the data) from a backend financialinstitution system using, for example, a financial institution mobileapplication and/or a mobile optimized website. At block 1612, a user mayconnect to a dynamic transaction card, for example, using Bluetooth™,BLE, RFID, WiFi, and/or other wireless networks by turning on pairingcapabilities of the dynamic transaction card and mobile device,searching for pairing devices, and connecting the two devices.

At block 1614, in response to a request for new card data, the accountholder's mobile device may receive, via a wireless network, new carddata from a backend financial institution system. At block 1614, the newcard data received at the mobile device may be transmitted to thecurrently paired dynamic transaction card, where it may be stored on amicrocontroller, microprocessor, and/or EMV™ processor. As discussedherein, new card data and/or new account data may be fully or partiallypre-loaded onto a dynamic transaction card. Accordingly, the receivednew card data may include only an activation signal that when receivedand executed on a microcontroller, microprocessor, and/or EMV™ processorof a dynamic transaction card, instructs the card to activate pre-storednew card data and/or pre-stored new account data.

At block 1616, a microcontroller may initialize an EMV™ processor withthe financial institution application ID. In this manner, the EMV™processor may associate a particular application ID associated with aspecific account application running on the dynamic transaction cardwith the new account data. At block 1618, an application running on thedynamic transaction card may update the active card data stored on thedynamic transaction card with the new account data received and/orpre-stored on the dynamic transaction card. At block 1620, theapplication running on the dynamic transaction card may transmit aresponse to the microcontroller to confirm that the active card datastored on the dynamic transaction card has been successfully updatedwith the new card data.

At block 1622, a microcontroller on the dynamic transaction card maytransmit the confirmation of a successful update to the mobile deviceassociated with the account holder via the paired wireless connection.This confirmation may then be transmitted from the mobile device to abackend financial institution system where the account data may beupdated to reflect the confirmation. Once confirmation that the accounthas been successfully activated on the dynamic transaction card isreceived at the backend financial institution system, the backendfinancial institution system may then change the status associated withthe new card data from inactive to active.

In an example embodiment, a dynamic EMV™ card may be used in conjunctionwith settings stored on a mobile device to provide a dynamic transactioncard interface that may be understood by users with visual/audioimpairments. For example, a user of a mobile device may provideimpairment setting to the mobile device, such as user device 140. Thesesetting may indicate a particular visual impairment, such asnearsightedness, farsightedness, glaucoma, or other visual impairments,or audio impairments. The impairment setting may be stored in memorywithin the mobile device (e.g., nonvolatile memory). The impairmentsetting may be transmitted along with a data alert to the dynamictransaction card via a network, such as WiFi, RFID, or BLE. Theimpairment setting may include instructions that when executed on thedynamic transaction card instruct the dynamic transaction card toillustrate the alert in a manner that may be understood by a user withthe indicated impairment. For example, a user with a visual impairmentmay require specific shapes, blinking patters, and/or colors to bestindicate and alert.

Various colors, symbols, and blinking patterns may be used based on theimpairment setting. In this manner, a monochromatic display may becomean RGB display to assist those with visual/audio impairments. As anexample, FIG. 17 illustrates a method 1700 that may be used to generatea display on a dynamic transaction card (such as card 200, 700) that maybe understood by a user with an impairment. The method may begin atblock 1702. At block 1704, a mobile device may receive a user settingindicating an impairment. The impairment setting may be stored in memoryassociated with the mobile device and/or dynamic transaction card. Atblock 1706, a connection may be made between the mobile device and thedynamic transaction card (e.g., WiFi, RFID, BLE, and the like). When adynamic transaction card is used in a transaction as described herein,the mobile device associated with the dynamic transaction card mayreceive data from a backend system storing account informationassociated with the dynamic transaction card and/or from the dynamictransaction card itself (block 1708). The data may indicate a balance, acredit limit, a budget balance, a transaction amount, and the like. Atblock 1710, the mobile device may generate alert data to transmit theinformation received from the backend server to the dynamic transactioncard for display (block 1712). The alert data that is generated mayinclude data that can instruct the dynamic transaction card to generatea visual display indicating the particular alert. The alert data alsomay include data that can instruct the dynamic transaction card togenerate a visual display specific to the impairment data.

For example, the data that is transmitted to the dynamic transactioncard may instruct the dynamic transaction card to, instead of displayingan alphanumeric value, display a specific symbol (e.g., circle, square,triangle, octagon, and the like), a specific color (e.g., red, yellow,green, blue, and the like), or a combination of symbols and colors(e.g., red octagon, green circle, and the like). The data that istransmitted to the dynamic transaction card may instruct the dynamictransaction card to display a pattern of blinking lights (e.g., fastblinking, slow blinking, blinking in a specific order, and the like) toindicate a balance, a credit limit, a budget balance, a transactionamount, and the like.

FIG. 18 illustrates a method 1800 that may be used to generate a displayon a dynamic transaction card (such as card 200, 700) that may beunderstood by a user with an impairment. The method 1800 may begin atblock 1802. At block 1804, a mobile device may receive a user settingindicating an impairment. At block 1806, a connection may be madebetween the mobile device and the dynamic transaction card (e.g., WiFi,RFID, BLE, and the like). At block 1808, the mobile device may transmitthe impairment setting to the dynamic transaction card, where it may bestored, for example, in nonvolatile memory. Storing the impairmentsettings in nonvolatile memory within the dynamic transaction card mayallow the dynamic transaction card to convert any alert or request fordata to be displayed on the dynamic transaction card to be converted onthe dynamic transaction card into a display of data that may be readilyunderstood by users with the impairment. For example, when a dynamictransaction card is used in a transaction as described herein, themobile device associated with the dynamic transaction card may receivedata from a backend system storing account information associated withthe dynamic transaction card and/or from the dynamic transaction carditself (block 1810). The data may indicate a balance, a credit limit, abudget balance, a transaction amount, and the like. At block 1812, themobile device may generate alert data to transmit the informationreceived from the backend server to the dynamic transaction card fordisplay. The alert data that is generated may include data that caninstruct the dynamic transaction card to generate a visual displayindicating the particular alert. Once received at the dynamictransaction card, the dynamic transaction card may convert the alertinto a display that may be readily understood by the user with theimpairment. For example, a display indicating a particular balance maybe altered from an alphanumeric display to a color/shape display thatmay indicate the particular balance. In this example, a balance that isat 75% of the limit may be indicated using a red octagon, whereas abalance that is 25% of the account limit may be indicated using a greencircle.

FIG. 19 illustrates an example method for using user authenticationinput recognition, which may be gesture recognition, to activate adynamic transaction card. The method 1900 may start at block 1902. Atblock 1904, user application 156 on user device 140 may receive anexemplar user authentication input, which may be a predetermined gestureor gesture sequence provided by a card user. The received predeterminedgesture may be utilized to configure or reset specific gestures forgesture recognition that may be used to activate dynamic transactioncard 120 by authenticating a card user. The predetermined gesture orgesture sequence may include rotation of the card 90 degrees clockwise,rotation of the card 180 degrees clockwise, a tap, double tap, longpress, flick, scroll, or pinch of the screen of user device 140, and thelike. The predetermined gesture may also include a biometric input(e.g., fingerprint, eye scan, gesture recognition, voice recognition,and/or the like), input indicative of a paired mobile device (e.g., BLEand/or Bluetooth™ pairing), input indicative of a password (e.g., apassword received via a sensor on the dynamic transaction card and/or apassword received on a paired mobile device), input indicative of asignature (e.g. a signature received via a sensor on the dynamictransaction card and/or a signature received on a paired mobile device,and/or the like.

At block 1906 the received predetermined gesture provided by a card usermay be securely stored on EMV™ chip 122, backend 318 system, and/or userauthentication system 160. A connection may be made between user device140 and dynamic transaction card 120 (e.g. WiFi, RFID, BLE, and thelike) and/or backend 318 system to transmit the predetermined gesturefrom user device 140 to dynamic transaction card 120, userauthentication system 160, and/or backend 318 system respectively forstorage.

At block 1908, dynamic transaction card 120 may receive input from asensor through a card user performed gesture. For example, a user mayprovide input to a touch sensor by performing a predetermined gesture,as described above, which may include tapping a location on dynamictransaction card 200 a specific number of times and/or for a specificlength of time (e.g., double tap, triple tap, one long tap followed byone short tap, and/or the like. The input may also include a biometricinput (e.g., fingerprint, eye scan, gesture recognition, voicerecognition, and/or the like), input indicative of a paired mobiledevice (e.g., BLE and/or Bluetooth™ pairing), input indicative of apassword (e.g., a password received via a sensor on the dynamictransaction card and/or a password received on a paired mobile device),input indicative of a signature (e.g. a signature received via a sensoron the dynamic transaction card and/or a signature received on a pairedmobile device, and/or the like. A user may also provide input to anaccelerometer, motion sensor, or gyroscope that detects the motion andchanges in the orientation of dynamic transaction card 200 by performinga predetermined gesture, as described above, which may include rotatingthe card 90 degrees clockwise or rotating the card 180 degreescounterclockwise.

At block 1910, in response to receiving sensor input, microcontroller224, user device 140, user authentication system 160, and/or backendsystem 318 may perform gesture recognition processing to determine if acard user should be authenticated for card usage, and as such whether toactivate dynamic transaction card 120. Microcontroller 224, user device140, user authentication system 160, and/or backend system 318 mayretrieve the predetermined gesture from EMV™ chip 122, userauthentication system 160, and/or backend system 318, and may utilizesoftware including gesture recognition algorithms, which may include apattern matching algorithm, that may compare the user performed gestureto the predetermined gesture. User device 140 may performcompression/decompression of the received sensor input. Backend system318 may process the received sensor input. At block 1912, ifmicrocontroller 224, user device 140, user authentication system 160,and/or backend system 318 determines that the user performed gesturematches the predetermined gesture, the dynamic transaction card may beactivated, which may include activating EMV™ chip 212 and/or a dynamictransaction card 200's magnetic stripe, thereby authenticating the carduser as authorized to use the card. At box 1914, if a match is notdetermined, a user may take a corrective action to perform anothergesture to be processed as illustrated in blocks 1908-1910 to attempt toauthorize the card user and dynamic transaction card. The method may endat block 1916.

FIG. 20 illustrates an example method for using user authenticationinput recognition, which may be voice recognition to activate a dynamictransaction card according to embodiments of the disclosure. The method2000 may start at block 2002. At block 2004, user application 156 onuser device 140 may receive an exemplar user authentication input, whichmay be predetermined voiceprint of a pass phrase spoken by a card user.The received predetermined voiceprint may be utilized to configure orreset specific voiceprints for voice recognition that may be used toactivate dynamic transaction card 120 by authenticating a card user.

At block 2006 the received predetermined voiceprint provided by a carduser may be securely stored on EMV™ chip 122, user authentication system160, and/or backend 318 system. A connection may be made between userdevice 140 and dynamic transaction card 120 (e.g. WiFi, RFID, BLE, andthe like), user authentication system 160, and/or backend 318 system totransmit the predetermined voiceprint from user device 140 to dynamictransaction card 120, user authentication system 160, and/or backend 318system respectively for storage.

At block 2008, dynamic transaction card 120 may receive a userauthentication input from a microphone through a user spoken voiceprint.At block 2010, in response to receiving sensor input, microcontroller224, user device 140, user authentication system 160, and/or backendsystem 318 may perform voice recognition processing to determine if acard user should be authenticated for card usage, and as such whether toactivate dynamic transaction card 120. Microcontroller 224, user device140, user authentication system 160, and/or backend system 318 mayretrieve the predetermined gesture from EMV™ chip 122, userauthentication system 160, and/or backend system 318, and may utilizesoftware including voice recognition algorithms, which may include apattern matching algorithm, that may compare the user spoken voiceprintto the predetermined voiceprint. User device 140 may performcompression/decompression of the received sensor input. Backend system318 may process the received sensor input. At block 2012, ifmicrocontroller 224, user device 140, user authentication system 160,and/or backend system 318 determines that the user spoken voiceprintmatches the predetermined voiceprint, the dynamic transaction card maybe activated, which may include activating EMV™ chip 212 and/or adynamic transaction card 200's magnetic stripe, thereby authenticatingthe card user as authorized to use the card. At box 2014, if a match isnot determined, a user may take a corrective action to speak anothervoiceprint to be processed as illustrated in blocks 2008-2010 to attemptto authorize the card user and dynamic transaction card. The method mayend at block 2016.

The user authentication processing described herein may be asymmetric.As such, simple user authentication inputs such as a tap gesture, wherean accelerometer may detect when a dynamic transaction card is tapped,may be processed by a dynamic transaction card, which may includeprocessing by a microcontroller. For more complex user authenticationinputs, which may include, for example, signatures, combined motions,sounds, and biometric data, the user authentication processing may beperformed by a dynamic transaction card 120, a user device 140, abackend system 318, and/or a user authentication system 160. Forexample, a dynamic transaction card may perform signal acquisition andfiltering of the signal generated from the user authentication input. Auser device may perform signal compression and decompression of thefiltered signal from the dynamic transaction card. A backend processingsystem which may be an authentication system may process the packageddata from the dynamic transaction card and user device associated withthe received user authentication input to determine if a card usershould be authenticated for card usage.

It is further noted that the systems and methods described herein may betangibly embodied in one of more physical media, such as, but notlimited to, a compact disc (CD), a digital versatile disc (DVD), afloppy disk, a hard drive, read only memory (ROM), random access memory(RAM), as well as other physical media capable of storing software, orcombinations thereof. Moreover, the figures illustrate variouscomponents (e.g., servers, computers, processors, etc.) separately. Thefunctions described as being performed at various components may beperformed at other components, and the various components bay becombined or separated. Other modifications also may be made.

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its spirit and scope, as may be apparent.Functionally equivalent methods and apparatuses within the scope of thedisclosure, in addition to those enumerated herein, may be apparent fromthe foregoing representative descriptions. Such modifications andvariations are intended to fall within the scope of the appendedrepresentative claims. The present disclosure is to be limited only bythe terms of the appended representative claims, along with the fullscope of equivalents to which such representative claims are entitled.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only, and is not intendedto be limiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It may be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It may be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent may be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, suchrecitation should be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, means at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It may be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” may be understood toinclude the possibilities of “A” or “B” or “A and B.”

The foregoing description, along with its associated embodiments, hasbeen presented for purposes of illustration only. It is not exhaustiveand does not limit the invention to the precise form disclosed. Thoseskilled in the art may appreciate from the foregoing description thatmodifications and variations are possible in light of the aboveteachings or may be acquired from practicing the disclosed embodiments.For example, the steps described need not be performed in the samesequence discussed or with the same degree of separation. Likewisevarious steps may be omitted, repeated, or combined, as necessary, toachieve the same or similar objectives. Accordingly, the invention isnot limited to the above-described embodiments, but instead is definedby the appended claims in light of their full scope of equivalents.

In the preceding specification, various preferred embodiments have beendescribed with references to the accompanying drawings. It may, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded asan illustrative rather than restrictive sense.

The invention claimed is:
 1. A dynamic transaction card comprising: anouter protective layer having an outer edge; a card backing having anouter edge, wherein the card backing outer edge and the outer protectivelayer are connected to one another along the respective outer edges toform a casing for the components of the dynamic transaction card;wherein the components of the dynamic transaction card include: aEuroPay-MasterCard-visa (EMV™) chip comprising an EMV™ plate accessiblefrom the outer protective layer and an EMV™ processor; an antenna tosend and receive wireless communications; a microcontroller to: receive,via the antenna, an exemplar input comprising an activation gestureinputted into a mobile device; authenticate a user of the dynamictransaction card based on a first match between an input comprising acard gesture performed by the user with the dynamic transaction card andthe exemplar input, the activation gesture and the card gesturecomprising an altered orientation and/or position of the dynamictransaction card to activate the dynamic transaction card; and activatethe dynamic transaction card based on the first match; a magnetic stripestoring tracks of data that are utilized to conduct a transaction; asensor, comprising an accelerometer, a motion sensor, or a gyroscope todetect the input and the exemplar input; a display component that isvisible through or extends through the outer protective layer andincludes a dot matrix display, one or more LED lights, one or more OLEDlights, electronic paper, Mirasol, TF LCD, and/or Quantum Dot Display,wherein the display component generates a predefined pattern in responseto receiving data from a transaction terminal or an account holderdevice based on display settings; and an energy storage component topower the dynamic transaction card.
 2. The dynamic transaction card ofclaim 1, wherein the microcontroller, the mobile device, a userauthentication system and/or a backend system compares the input tomultiple exemplar inputs associated with multiple card users todetermine if the dynamic transaction card should be activated.
 3. Thedynamic transaction card of claim 2, wherein the microcontrollerperforms signal acquisition and filtering of the input.
 4. The dynamictransaction card of claim 3, wherein the mobile device performs signalcompression and decompression of the signal filtered by themicrocontroller.
 5. The dynamic transaction card of claim 4, wherein theuser authentication system and/or the backend system processes datapackaged from the input to authenticate the user.
 6. The dynamictransaction card of claim 1, wherein the microcontroller activates thedynamic transaction card by activating the EMV™ chip and/or magneticstripe.
 7. The dynamic transaction card of claim 1, wherein the exemplarinput is configured on a mobile application on the mobile device.
 8. Thedynamic transaction card of claim 7, wherein the exemplar input isstored on the EMV™ chip, a user authentication system and/or a backendsystem.
 9. The dynamic transaction card of claim 1, wherein the sensorincludes a touch sensor, a light sensor, a heat sensor, a piezoelectricsensor, and/or load cells.
 10. The dynamic transaction card of claim 9,wherein the activation gesture includes a tap, long press, flick,scroll, and/or pinch inputted into the mobile device, and wherein thecard gesture includes a tap, long press, flick, scroll, and/or pinchperformed with the dynamic transaction card.
 11. The dynamic transactioncard of claim 1, wherein the microcontroller, the mobile device, a userauthentication system and/or a backend system uses gesture recognitionprocessing to compare the card gesture to the exemplar input todetermine if the dynamic transaction card should be activated.
 12. Thedynamic transaction card of claim 11, wherein the microcontrollerperforms signal acquisition and filtering of the input.
 13. The dynamictransaction card of claim 12, wherein the mobile device performs signalcompression and decompression of the signal filtered by themicrocontroller.
 14. The dynamic transaction card of claim 13, whereinthe user authentication system and/or the backend system processes datapackaged from the input to authenticate the user.
 15. The dynamictransaction card of claim 1, wherein the components of the dynamictransaction card further include: a microphone to receive a spokenvoiceprint from the user; and the microcontroller to further: receive,via the antenna, an exemplar voiceprint from the mobile device; andauthenticate the user based on a second match between the spokenvoiceprint received at the microphone and the exemplar voiceprint. 16.The dynamic transaction card of claim 15, wherein the microphone isconstructed out of a piezoelectric element or a bimorph element.
 17. Thedynamic transaction card of claim 15, wherein the microcontroller, themobile device, a user authentication system and/or a backend system usesvoice recognition processing to compare the spoken voiceprint to theexemplar voiceprint to determine if the dynamic transaction card shouldbe activated.
 18. The dynamic transaction card of claim 17, wherein themicrocontroller performs signal acquisition and filtering of the spokenvoiceprint.
 19. The dynamic transaction card of claim 18, wherein themobile device further performs signal compression and decompression ofthe spoken voiceprint.
 20. The dynamic transaction card of claim 19,wherein the user authentication system and/or the backend systemprocesses data packaged from the spoken voiceprint to authenticate theuser.